[Top][All Lists]

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

Re: [request] info: don't allow ^C to quit the program

From: Gavin Smith
Subject: Re: [request] info: don't allow ^C to quit the program
Date: Wed, 24 May 2017 18:36:23 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

On Wed, May 24, 2017 at 10:51:33AM +0200, Benno Schulenberg wrote:
> When someone who is not familiar with info tries it out,
> types something, and gets stuck, he will type ^C to get
> unstuck.  This has the unfortunate effect that it quits
> the program.  It would be better if this key were bound
> by default to key-abort.  This would also make --vi-keys
> more useful.

They may be typing ^C because they want to quit.  I don't see the need
to change it as ^C has always quit info and changing it now will be
disruptive to anyone who wanted to quit using ^C.  Many other programs
are also closed by ^C, as it takes work to stop ^C from quitting (as 
changing the terminal settings is necessary to stop this).  In fact, it 
could be quite frustrating for someone who wants to quit and can't work 
how to do so.

> To "compensate" for the loss of a quit key, I would suggest
> to bind also ^Q to quit.  (The key is currently not bound,
> and many programs respond to ^Q, so why not info too?)

I don't know what programs you mean, but I doubt anyone will think of
this without reading it in the manual.

> And when adding some generally known bindings anyway,
> maybe also add ^W for delete-window?

I doubt that the "window" feature of info is much used.  (If info were
being written now, I would advise not to include it, as it is a needless 
complication.)  I don't think it is worth using up another key for a 
window command.  (Who knows, maybe ^W will be wanted as a key for 
another command at some point.) There is no need to add another binding 
for this, as it has a key binding already ('C-x 0').  If it was added, 
it would have to be mentioned in the manual, wasting the time and mental 
attention of everyone who looks at it.

reply via email to

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