[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 02:44:09 +1100

Branden, what terminal are you using? I would like to try the same. I guess Ubuntu is quite close to Debian in that respect.
1. I tried different terminals and even SSH.
2. What modes can be relevant?
3. I never heard of any relevant configuration options of bash. What could it be?
Also "stty" settings are OS-standard.

Control-V does not have any delay. It just quotes the next character - whatever and whenever it comes. Even if I input that after an hour; no matter if it's just ESC or an escape sequence.
So this is not helpful here.

I can easily imagine that the whole escape-sequence may not be available for the reader right away, depending on the terminal, modes, etc. For example, with limited baud rate the sequence will always be read by one character.
But I am pretty sure there is no any significant delay between the characters. Not even 1ms.

There is also a possibility of some custom build settings or patches in these OSes.
Readline version here is: 6-6.3

On Mon, Nov 13, 2017 at 1:51 AM, G. Branden Robinson <address@hidden> wrote:
At 2017-11-13T01:38:11+1100, Yuriy Ershov wrote:
> 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?

I tested it before I sent it.  I'm running Debian 9 "Stretch".
Something is going wrong on your system.

Unfortunately the terminal handling pipeline in pretty deep.  There
could be a problem with:

* your terminal emulator (I use XTerm);
* your terminal "modes" (how the kernel talks to your terminal
  emulator); and/or
* your Bash configuration.

The first and last are easy to rule in or out by trying different
terminal emulators and shells, respectively.  Control-V should work
everywhere to "quote the next character".  You can then type Control-V
followed by Escape and then (quickly) the next key in the sequence.
If they appear together, it's working as intended.  If not, you're
taking too much time between pressing Escape and the next key in the


reply via email to

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