On 9/27/18 12:15 PM, Richard Todd wrote:
> On Thu, Sep 27, 2018 at 11:08:19AM -0400, Chet Ramey wrote:
>> On 9/26/18 4:36 PM, Richard Todd wrote:
>>> I noticed in vi-mode, if you search with 't'/'T', then readline
>>> gets stuck on ';' (because the next letter already matches). So,
>>> from the start of this paragraph, I would expect 'te;' to take me
>>> to the 'd' in the word "vi-mode", rut readline gets stuck on the
>>> 'c' in "noticed" instead.
>>
>> Thanks for the report. It seems to me that readline implements what the
>> POSIX standard wants for t/T, but I'll take a closer look.
>
> Now that you've said that, I realize that the behavior I am after is actually
> a
> vim enhancement. When I turn on vi-compatibility mode, the cursor gets stuck
> when trying to repeat a t/T search just as it does in readline. I should have
> checked that before I posted the report--I guess I've been running vim too
> many
> years!
I wonder if an `extended-vi' option is the way to handle this.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/
_______________________________________________
Bug-readline mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-readline
