Re: [Bug-readline] problem after upgrade to 6.3

[Nuzhna Pomoshch]

On Tue, 10/4/16, Chet Ramey <address@hidden> wrote:
> Subject: Re: [Bug-readline] problem after upgrade to 6.3
> To: "Nuzhna Pomoshch" <address@hidden>, address@hidden
> Cc: address@hidden
> Date: Tuesday, October 4, 2016, 6:07 PM

>>> On Sun, 9/18/16, Chet Ramey <address@hidden> wrote:
>>> Subject: Re: [Bug-readline] problem after upgrade to 6.3
>>> To: "Nuzhna Pomoshch" <address@hidden>, address@hidden
>>> Cc: address@hidden
>>> Date: Sunday, September 18, 2016, 11:22 PM
>> 
>> Thank you for your reply.
>> 
>>> It's not all that mysterious.  Your DEL key outputs the key sequence
>>> "^[[3~" (ESC, [, 3, ~).  That key sequence isn't bound to anything by 
>>> default.
>>> If readline finds the string assigned to the termcap `kD' (terminfo `kdch1')
>>> capability, it will bind it to delete-char, but it doesn't appear that this 
>>> is the
>>> case on your system. It's done this since at least bash-3.1/readline-5.1.
>> 
>> Understand only a little of that.
>> 
>> My /etc/inputrc has:
>> 
>> "\e[3~": delete-char
>> 
>> Is that correct?

> It should be.  You can verify whether or not that has actually been read
> and is active by running
>
> bind -m vi-command -p | grep delete-char

Sorry to bother you again, but I am still having problems with this,
and I have literally spent hours trying to learn about it.

It LOOKS like it should work the way I want, but it doesn't.

On a machine running readline 6.2 (where everything is working correctly):

$ bind -m vi-command -p | grep delete-char
# backward-delete-char (not bound)
"\e[3~": delete-char
# delete-char-or-list (not bound)
# forward-backward-delete-char (not bound)

On a machine running readline 6.3:

$ bind -m vi-command -p | grep delete-char
# backward-delete-char (not bound)
"\e[3~": delete-char
# delete-char-or-list (not bound)
# forward-backward-delete-char (not bound)

You will note that those are identical, yet (still) hitting the delete key
(at the end of the line) pops up (arg: 3) on the readline 6.3 machine.

Any other ideas as to what could be causing this?

Thank you again.

Nuzhna