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: Tue, 4 Oct 2016 14:07:07 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0

On 10/2/16 8:05 PM, Nuzhna Pomoshch wrote:
> --------------------------------------------
>> 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

-- 
``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]