Eric Kow wrote:
>> Is it worth documenting somewhere that j/k are used because of vim?
>
> I think just repeating the hints are fine, or even just three words ("as in
> Vi")
Probably a good idea. I think that j/k, in addition to being well known
from vi, were also chosen here because they are rarely used in mnemonics
and don't clash with more useful mnemonic letters like n/p would.
>> Also, are these bindings annoying for non-QWERTY users?
>
> Not that we can do very much about it, but I can report from using Vim
> on three layouts (mostly Dvorak):
>
> Dvorak: mostly OK because jk are next to each other and h is
> to the left of l
> Azerty: same as QWERTY
> Bépo: chaos ensues :-) [I don't use Bepo enough to know if it's a problem]
>
I use Colemak at this point (I'm quite happy with it). In Colemak j and
k are both index finger keys on the inside/stretch column. This puts
them in an actual "up/down" relationship, but unfortunately they are
inverted with j above k. I've grown used to the inversion at this point
thanks to the few tools that use vim-like bindings without rebinding
support like Google's applications and darcs...
A couple of obvious questions to me:
* Would there be enough interest in mnemonic rebinding support (for
crazy and/or power users) to be worth the time to implement it? (Would
also help with l10n if that ever started to matter to darcs...)
* With haskelline would it be possible to support (on terminals that
support it, naturally) the actual up/down arrow keys (although that
might be confusing from a "readline" standpoint) and/or Page Up/Page
Down as "more natural" (to non-vi user) counterparts to j/k?
--
--Max Battcher--
http://worldmaker.net
|