[Top][All Lists]

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

Re: [Bug-readline] Control-O keybinding does not work [with patch]

From: Chet Ramey
Subject: Re: [Bug-readline] Control-O keybinding does not work [with patch]
Date: Thu, 18 Jan 2018 07:42:51 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 1/17/18 12:02 PM, Rhialto wrote:
> On Wed 17 Jan 2018 at 11:42:45 -0500, Chet Ramey wrote:
>> On 1/17/18 10:25 AM, Rhialto wrote:
>>> I entered a bug report against bash here:
>>> http://savannah.gnu.org/support/index.php?109449                            
>>> see also 
>>> http://mail-index.netbsd.org/pkgsrc-users/2018/01/16/msg026141.html 
>>> but it's really a problem of the included readline.
>> Bash adds the ^O binding, so there's no reason for readline to disable
>> the special character. It's not available to other applications using
>> readline.
> I don't understand what you're getting at. Any user of readline can make
> a mapping of ^O to do something. Bash is just where I discovered that it
> doesn't work. As it is, ^O is interpreted by the operating system, and
> readline will never see it.
> You can't expect users of readline to somehow "fix" readline's tty
> handling so that their mapping starts working...

OK. The logical conclusion of your argument is that readline should disable
all tty special characters because there is a possibility that a user or
an application will add a binding for them, even though readline doesn't
use that binding itself.

Readline binds most of the tty special characters to its own, mostly
equivalent, bindings. Why should it touch a character for which it doesn't
provide a replacement, removing functionality users have always been able
to rely on? That's not reasonable.

What is reasonable is to expect an application (or a user) to make sure the
key sequence it wants to use is available in those cases where readline
doesn't use it.

Bash doesn't have any functions to change the tty settings persistently,
so the easiest thing for a user to do is to use `stty' to disable the tty
special character for ^O. That's what I do.


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

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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