> Never mind how I pull in the legacy key bindings. The main reason I
> chimed in is to contribute feedback about what bindings should be
> considered legacy or not. I don't have a problem reducing the size of
> the default bindings list. But I just thought I'd mention that the
> "infrequent" characterization for 'a', 'b', 'e' and to some degree 'L'
> is not true in my case. If I'm an outlier, that's fine, but it's hard
> to determine what bindings people use on a daily basis if they don't
> speak up - so I did ;)
In that case, my general principle is that the users are the best judge of
how best to bind keys for their own use. The purpose of the package's
default key bindings is firstly to help out the new users and secondly to
bring in some amount of standardization. So, the functions that are not
needed for the majority of the users the majority of the time are best to
left to the users to bind for themselves.
Some very useful functions never get used unfortunately because they are
impractical to use unless bound to keys. An excellent example is
vm-quit-just-bury, which I bind to `b' for my own use. Freeing up keys will
allow users to explore various possibilities.
John Hein writes:
> Never mind how I pull in the legacy key bindings. The main reason I
> chimed in is to contribute feedback about what bindings should be
> considered legacy or not. I don't have a problem reducing the size of
> the default bindings list. But I just thought I'd mention that the
> "infrequent" characterization for 'a', 'b', 'e' and to some degree 'L'
> is not true in my case. If I'm an outlier, that's fine, but it's hard
> to determine what bindings people use on a daily basis if they don't
> speak up - so I did ;)
In that case, my general principle is that the users are the best judge of
how best to bind keys for their own use. The purpose of the package's
default key bindings is firstly to help out the new users and secondly to
bring in some amount of standardization. So, the functions that are not
needed for the majority of the users the majority of the time are best to
left to the users to bind for themselves.
Some very useful functions never get used unfortunately because they are
impractical to use unless bound to keys. An excellent example is
vm-quit-just-bury, which I bind to `b' for my own use. Freeing up keys will
allow users to explore various possibilities.
Cheers,
Uday