[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-readline] Custom vi mode bindings causes problems with some bui
Re: [Bug-readline] Custom vi mode bindings causes problems with some builtin commands
Mon, 22 Jun 2015 19:25:41 -0300
Thank you very much Chet for looking into this.
Just out of curiosity, I would like to ask you about the way some
aspects of the vi bindings work:
1) Some commands are mapped twice: say vi-change-to is bound both to c
and C. Does readline depends on the binding order to tell c appart
from C? Should vi-change-to and similar commands always be mapped to
the same key, except for the case?
2) Some more complex commands are mapped n times: say vi-char-search
to t, T, f, F, ; and ,! A fortiori: does readline depends on the order
or another internal convention to identify which "subcommand" of
vi-char-search to invoke?
On Mon, Jun 22, 2015 at 3:54 PM, Chet Ramey <address@hidden> wrote:
> On 6/22/15 1:16 PM, Carlos Pita wrote:
>> Defining bindings for "operators" like d and c (v.g. daw and caw, see
>> the recipe below) wreaks havoc with the dd, cc, and <dot> (vi-redo)
>> commands in readline vi mode.
> The mechanism used to allow longer key sequences to `shadow' but still
> allow prefixes of those sequences to be bound to other commands discards
> part of the original (shorter) key sequence. This doesn't usually matter,
> except when you need it -- like, say, with the vi-mode `d', `c', and `y'
> commands. I'll have to figure out the best way to fix this.
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
> ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU address@hidden http://cnswww.cns.cwru.edu/~chet/