All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: James Lockie <bjlockie@lockie.ca>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: escape key]
Date: Sat, 16 Dec 2006 08:45:42 +0000	[thread overview]
Message-ID: <20061216084542.GD4049@ucw.cz> (raw)
In-Reply-To: <4580E985.2090208@lockie.ca>

Hi!

> >>>From: James Lockie <bjlockie@lockie.ca>
> >>>To: linux-x86_64@vger.kernel.org
> >>>Subject: escape key
> >>>Date: 	Tue, 12 Dec 2006 14:57:57 -0500
> >>>
> >>>I can't use the escape key to exit a menu with make 
> >>>menuconfig on kernel-2.6.19 or .1
> >>>It works on 2.6.18. :-(
> >>>      
> >
> >Is this a problem?
> >
> >You can exit a menu by selecting <Exit> and pressing 
> >Enter
> >or (as the help text at the top of the screen says:)
> >pressing <Esc><Esc> (2 times).  Yes, pressing <Esc> one 
> >time
> >and then waiting for 1-2 seconds used to exit a menu.
> >
> >One could argue that it has been "fixed" to match the 
> >help text.

> Two escapes works now. :-)

Actually could we fix our consoles, somehow, to make esc usable?
Having important key like esc unusable on consoles is quite ugly.

ioctl(console_fd, AM_I_IN_THE_MIDDLE_OF_ESCAPE_SEQUENCE_?) would do
the trick at least for vt consoles...
							Pavel
-- 
Thanks for all the (sleeping) penguins.

  reply	other threads:[~2006-12-16  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14  1:04 [Fwd: escape key] Sergio Monteiro Basto
2006-12-14  5:41 ` Randy Dunlap
2006-12-14  6:04   ` James Lockie
2006-12-16  8:45     ` Pavel Machek [this message]
2006-12-16 18:34       ` Jan Engelhardt
2006-12-17  0:51         ` Stephen Clark
2006-12-17  9:40           ` Jan Engelhardt
2006-12-18  1:21         ` James Cloos
2006-12-18 14:02           ` Stephen Clark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061216084542.GD4049@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bjlockie@lockie.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.