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

[Nuzhna Pomoshch]

> On Mon, 5/29/17, Chet Ramey <address@hidden> wrote:

> > On 5/28/17 3:29 PM, Nuzhna Pomoshch wrote:

> > $ 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?
 
> OK, I think I got it. I was able to reproduce it with this additional
> detail. The issue is a failing readline command (delete-char with no chars
> to delete, in this case) at the end of a multi-key sequences. The problem
> is that readline wrongly chooses to back up the key sequence because the
> command doesn't return 0. Readline needs to better validate the return code
> before backtracking. This will be fixed in the next bash and readline devel
> branch pushes.

Can you tell me what versions this will be fixed in?

I am still seeing the problem in readline-7.0_p3 and bash-4.4_p12

Thanks.

Nuzhna