From: Stephen Clark <Stephen.Clark@seclark.us>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Pavel Machek <pavel@ucw.cz>, James Lockie <bjlockie@lockie.ca>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: escape key]
Date: Sat, 16 Dec 2006 19:51:35 -0500 [thread overview]
Message-ID: <45849497.7070206@seclark.us> (raw)
In-Reply-To: <Pine.LNX.4.61.0612161922530.30896@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>On Dec 16 2006 08:45, Pavel Machek wrote:
>
>
>>>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.
>>
>>
>
>It's something between a misdesign and a misconfiguration of the ESC key.
>
>In other words, many unices make ESC generate ^[, the general
>terminal escape character that is _also_ generated by keys like "up",
>^[[A.
>
>MS-DOS, or rather QBASIC's, Turbo BASIC's and other implementation of
>keys, does not have this "bug": here ESC generates "\x1B" and "up"
>generates "\x00H" IIRC. There is no key defined to generate "\x00".
>=> All fits nicely.
>
>So I see two steps:
>
> - making ESC generate something else than ^[, or making function
> keys do something else
>
> - fixing the terminfo description and the xterms
>
> - possibly creating a new termtype ("linux2" or "xterm2") so as to
> not tamper with compatibility
>
>Then text-console graphic applications (ncurses, slang, etc.) would
>not need to wait the defined one second for an escape sequence to
>complete.
>
>HOWEVER, unix people probably _had a reason_ to make ESC generate
>part of what function keys do. Should my UP key go broke, I could
>still - though probably tedious - reproduce it by hitting the three
>keys ESC [ A. Problem, as pointed out, is that ESC has long been used
>by the majority of people back then for something else than doing
>terminal sequences by hand: DOS, apps, games, Windows GUIs, and,
>I suppose, even X11.
>
>
>
> -`J'
>
>
Hi,
do man ascii - ESC is 0x1b.
Thats what the esc key should generate - it sometimes echoed as ^[
because the [ = 0x5b
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2006-12-17 0:58 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
2006-12-16 18:34 ` Jan Engelhardt
2006-12-17 0:51 ` Stephen Clark [this message]
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=45849497.7070206@seclark.us \
--to=stephen.clark@seclark.us \
--cc=bjlockie@lockie.ca \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox