[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug: 'vi-fword' binding command does the same as 'vi-fWord'

From: Chet Ramey
Subject: Re: bug: 'vi-fword' binding command does the same as 'vi-fWord'
Date: Sun, 29 Dec 2019 20:26:24 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.3.1

On 12/29/19 8:07 PM, Andrey Butirsky wrote:
> On 30.12.2019 03:11, Chet Ramey wrote:
>> On 12/29/19 3:45 PM, Andrey Butirsky wrote:
>>> Hi,
>>> the bug is: if any Readline binding command names differs only in
>>> character's case, these commands is indistinguishable and do the same
>>> function.
>>> For example, 'vi-fword' binding command erroneously does the same as
>>> 'vi-fWord' one, that is - jumps on "big" (space separated) words; while it
>>> is alias of||"vi-forward-word" command and as such should jump on a "small"
>>> vi words. For 'vi-fWord', "vi-forward-bigword" alias exists:
>> Yes, you should always use the `long' names. The short versions exist only
>> because they always have. The long versions were added in
>> bash-4.2/readline-6.2 to solve exactly this problem.
> Of course, after digging into the code, I know now what the problem is and
> how to workaround it.
> But can we try to fix it? It's literally the bug just from the code.

That's the thing: it's not a bug. Function name matching is
case-insensitive, and always has been. This goes back as far as I can easily
check right now, and even predates vi mode.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]