6 ms·
been a long time i3 user mostly for the sane defaults. It requires significantly less fiddling than any other window manager I've tried out.
by Barrin92 7y ago
been a long time i3 user mostly for the sane defaults. It requires significantly less fiddling than any other window manager I've tried out.
- jolmg 7y agoWith exception of the directional keybindings. I wonder how it came to be that the defaults are "jkl;" for the directions instead of the "hjkl" used by everything else (vi(m), less, shells, repls, etc.).
- awake 7y agoh for help and your fingers rest on jkl; not hjkl if you are typing with proper form
- jolmg 7y agoWhen you're browsing text, though, it's more common to move up and down in text than it is to move sideways. If you're typing with proper form, "hjkl" results in the index finger moving down and the middle finger moving up. So, your most useful finger is used for the most common action, and your second most useful finger for the second most common action. What's probably the third most common action, moving left would be done with your index finger, and right with your ring finger. You'd never have to use your awkward pinky finger for anything. With "jkl;", you'd be moving down with the middle finger, and up with the ring finger. Your dexterious index finger would be waiting for the moment when you'd want to move left, which is not as often, and you'd be encouraged to use your awkward pinky finger quite often. This isn't necessarily the case when working with windows, but by now it's a matter of consistency. Although, encouraging to use the pinky finger and not being able to use the index finger for 2 actions still sucks.
- msoucy 7y agoProbably just QWERTY "home row" layout
- yyhhsj0521 7y agoIt seems that the intention was to emulate Vim [0], maybe the author was not familiar with it and made a mistake? [0] https://github.com/i3/i3/commit/6d0071db197031845b5f77febc22718869770a97 https://github.com/i3/i3/commit/6d0071db197031845b5f77febc22...
- ppseafield 7y agoIIRC it was deliberate so that users wouldn't have to move off the home row. The User's Guide states this is the reasoning behind it. > To move the focus between the two terminals, you can use the direction keys which you may know from the editor vi. However, in i3, your homerow is used for these keys (in vi, the keys are shifted to the left by one for compatibility with most keyboard layouts). Therefore, $mod+j is left, $mod+k is down, $mod+l is up and $mod+; is right. https://i3wm.org/docs/userguide.html https://i3wm.org/docs/userguide.html
- jolmg 7y ago> in vi, the keys are shifted to the left by one for compatibility with most keyboard layouts I wonder where they got that idea. The keys are "hjkl" simply because they were inscribed with arrows in the machine Bill Joy used when creating vi[1][2]. From [1]: > Joy used a Lear Siegler ADM-3A terminal... the keys h,j,k,l served double duty as cursor movement keys and were inscribed with arrows, which is why vi uses them in that way. The StackExchange question has a picture of the keys. [1] https://en.wikipedia.org/wiki/Vi#Creation https://en.wikipedia.org/wiki/Vi#Creation [2] https://vi.stackexchange.com/a/9315/14283 https://vi.stackexchange.com/a/9315/14283
- secure 7y agoI remember reading about that, but it must have been after I wrote that part of the userguide 11 years ago: https://github.com/i3/i3/commit/1fcad44f66926e679f4af6e4f4d6abcba700034c https://github.com/i3/i3/commit/1fcad44f66926e679f4af6e4f4d6... :) Can you send a PR for https://github.com/i3/i3/blob/30e886b0319ee948863a36a65e5b7283f6dd8938/docs/userguide#L59 https://github.com/i3/i3/blob/30e886b0319ee948863a36a65e5b72... with your correction please?
- calvinmorrison 7y agoi am always surprised when people do not have noremap ; l noremap l k noremap k j noremap j h
- deleted 7y ago[deleted]
- abjKT26nO8 7y agoHave you figured out how to make i3 move the mouse pointer to the area of the newly-focused window when you change window focus by keyboard? AwesomeWM does that out of the box. i3 doesn't and it's very annoying, because then when my table makes a microscopic movement and causes the mouse to move, suddenly what I'm typing is diverted to another window and weird things happen.
- jolmg 7y agoYou can fix that with: focus_follows_mouse no It doesn't do what you wanted, but I also can't see why anyone would want a window to focus simply because you hovered over it.
- zimmertr 7y agoI love that feature though!
- tmm 7y agoBecause why should I have to click to get focus? Less of an issue on a tiling window manager, but sometimes I really want to be able to type in a window without bringing it to the foreground. Also, selecting text should copy and middle click should paste. No one can convince me these things are bad or unnecessary.
- jolmg 7y ago> Because why should I have to click to get focus? The click not only focuses but is also passed on to whatever you clicked on, so it's like it was already focused. > Less of an issue on a tiling window manager, but sometimes I really want to be able to type in a window without bringing it to the foreground. I don't understand that. You have to somehow indicate to the system what it is you want to type on. > Also, selecting text should copy and middle click should paste. No one can convince me these things are bad or unnecessary. I'm 100% with you on that. Although saying "selecting text should copy" makes it sound like it's being copied when selecting, when it's actually copied when pasting.