3 ms·
I just use super(win key)/hyper (bound to capslock) for i3-related commands and leave emacs to its own devices with normal binds
by PunchyHamster 5mo ago
I just use super(win key)/hyper (bound to capslock) for i3-related commands and leave emacs to its own devices with normal binds
- royal__ 5mo agoYeah this is what I do. This article feels like crazy overengineering for something that's not really a problem
- dima55 5mo agoA dedicated key for all window-manager things is what people that have thought about it do (I use the "windows" key). But keyboard manufacturers haven't thought about it, so sometimes reasonable things aren't possible. I don't know.
- sudahtigabulan 5mo agoUnless you have RSI. Then it might be worth it. Depends on what hurts.
- rileymat2 5mo agoYes, I am misunderstanding the problem. The windows/mac command key leave shift, control and alt free for i3.
- noosphr 5mo agoThere can never be too many modifier keys: https://xcancel.com/octonion/status/1341113219142828039 https://xcancel.com/octonion/status/1341113219142828039
- topaz0 5mo agoThat's fine as far as it goes, but I don't think that gets you what this article is for, which is things like using the same binding context-dependently to navigate between emacs splits and regular window manager windows, context-dependently. Which is a fun bit of overengineering.
- PunchyHamster 5mo agoYes, the entire point would be to avoid such brittle engineering and entanglement of the two
- krupan 5mo agoThe problem some of us have is we get used to jumping between emacs windows/buffers using C-x o and C-x b and then without thinking about it try and use the same keys to jump between i3 windows and of course it doesn't work. Or vice versa, trying to use i3 shortcuts to switch emacs windows/buffers.