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

[Nuzhna Pomoshch]

--------------------------------------------
> 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?
 
> Your erase key is ^H.  I presume that's what the erase/rubout key on
> your keyboard produces.

That sounds right. The bashrc file has:

stty erase '^H'

> When you press DEL, it outputs the key sequence above.  The sequence
> isn't bound to anything, so each character is treated separately.  The ESC
> takes you into vi command mode, the `[' is unbound, the `3'  introduces
> a digit argument, and the ~  command toggles case.

Is there some way to fix that? Where can I see the bindings?
 
> If the version of readline-6.2 released by your vendor binds
> that sequence to delete-char, you'll get  the behavior you observe.

I am using Gentoo, and I don't know that they changed anything (certainly
nothing in the build script). As I said before, the vanilla build of every 
version
up to 6.2 does not produce that behavior ("works correctly"), and 6.3 does
(without changing anything else on the machine.

If there is some configuration setting to fix it, I would be extremely grateful.

Thank you again.

Nuzhna