[Top][All Lists]

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

Re: [Bug-readline] {forward,reverse}-search-history binding bug

From: Yuriy Ershov
Subject: Re: [Bug-readline] {forward,reverse}-search-history binding bug
Date: Mon, 13 Nov 2017 01:38:11 +1100

Branden, thank you for your reply.
As I said, that does not work for me.
What I get is - search mode with empty string. I.e. any binding that starts with ESC key is unusable for that purpose because the search string gets reset.

I have tested this on Ubuntu and Mac OS. The behavior is identical and wrong.

Can you please try that on your machine?


On Mon, Nov 13, 2017 at 12:48 AM, G. Branden Robinson <address@hidden> wrote:
At 2017-11-12T18:49:50+1100, Yuriy Ershov wrote:
> So.. Guys, this is really easy to reproduce.
> Can someone confirm this is a bug?
> Or else pease tell me how do I map a key sequence starting with ESC (which
> is essentially any sane key/combination) to the *-search-history command.

bind '"\ez": forward-search-history'

...maps forward-search-history to Escape Z.

You can confirm that the binding is absent or present by running:

bind -q | grep z

before and after the binding command, respectively.

Note that incremental searches don't wrap the command history, so
forward-search-history is only useful after the history search "cursor"
(not the command-line cursor) is far enough back to match something.
One generally gets it there with reverse-search-history (C-s) first.


reply via email to

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