3 ms·
Those keybindings tend to deviate quite a lot in what they do from the originals, to the point of feeling almost random. Using the same keys as Vim for your cus
by johncoltrane 3y ago
Those keybindings tend to deviate quite a lot in what they do from the originals, to the point of feeling almost random. Using the same keys as Vim for your custom keybindings doesn't make them "Vim Keybindings".
`j` to jump to next post in Reddit is not "Vim-like" at all for someone familiar with Vim.
- almog 3y ago> `j` to jump to next post in Reddit is not "Vim-like" at all for someone familiar with Vim. Why not? For me the verb (motion) is down and noun is the post (I just think of each post as a line).
- johncoltrane 3y ago> I just think of each post as a line That's where the deviation occurs and where the idea of shared keybindings universe falls appart. Yes you have `j` in vi and Vim and `j` in Reddit, but they actually do different things, which requires a tiny bit of mental gymnastics… which is exactly what having the same keybindings everywhere is supposed to prevent.
- chrismorgan 3y agoj to go to the next item in a list is sufficiently Vim-like. Even j is not just one screen line like you’re expecting if you have 'wrap' enabled—that’s gj. Really, it’s simple domain mismatch. In Vim, gj/gk for physical lines, j/k for logical lines, (/) for sentences, {/} for paragraphs, [[/][/][/]] for sections as they are in certain families of languages. It’s all clearly designed for plain text navigation. Things like Reddit or an email client or whatever, {/} might be semantically a touch closer, but they’re still not exact matches, and all up j/k is extremely reasonable.
- johncoltrane 3y agoVi's and Vim's commands are the result of decades of extreme specialization. To the point that it seems ludicrous to even consider going the other way and generalizing them to all kinds of unrelated problems. There is too much domain mismatch, as you put it, for such a thing to be really _useful_.