bug-readline
[Top][All Lists]
Advanced

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

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


From: Chet Ramey
Subject: Re: [Bug-readline] problem after upgrade to 6.3
Date: Sun, 18 Sep 2016 19:22:34 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

On 9/18/16 9:45 AM, Nuzhna Pomoshch wrote:
> Reported this in 201507:
> 
> http://lists.gnu.org/archive/html/bug-readline/2015-07/msg00000.html
> 
> http://lists.gnu.org/archive/html/bug-readline/2015-07/msg00001.html

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.

Your erase key is ^H.  I presume that's what the erase/rubout key on
your keyboard produces.

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.

If the version of readline-6.2 released by your vendor binds that sequence
to delete-char, you'll get the behavior you observe.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/



reply via email to

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