[Fwd: escape key]
-------- Forwarded Message --------
Quoted 13 lines
From: James Lockie <[email protected]>
To: [email protected]
Subject: escape key
Date: Tue, 12 Dec 2006 14:57:57 -0500I 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. :-(-
To unsubscribe from this list: send the line "unsubscribe linux-x86_64" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 1 line
Sérgio M.B.
Quoted 9 lines · On Thu, 14 Dec 2006 01:04:50 +0000 Sergio Monteiro Basto wrote:
-------- Forwarded Message --------
Quoted 8 lines
From: James Lockie <[email protected]>
To: [email protected]
Subject: escape key
Date: Tue, 12 Dec 2006 14:57:57 -0500I 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.
---
~Randy
Quoted 21 lines · Randy Dunlap
Quoted 10 lines · On Thu, 14 Dec 2006 01:04:50 +0000 Sergio Monteiro Basto wrote:
-------- Forwarded Message --------
Quoted 8 lines
From: James Lockie <[email protected]>
To: [email protected]
Subject: escape key
Date: Tue, 12 Dec 2006 14:57:57 -0500I 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.
Quoted 6 lines
One could argue that it has been "fixed" to match the help text.
---
~Randy
Two escapes works now. :-)
Hi!
Quoted 19 lines
Quoted 19 lines
Quoted 9 lines
Quoted 9 lines
From: James Lockie <[email protected]>
To: [email protected]
Subject: escape key
Date: Tue, 12 Dec 2006 14:57:57 -0500I 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.
Quoted 4 lines
Quoted 2 lines
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
Signature · 1 line
Thanks for all the (sleeping) penguins.
Quoted 5 lines · Pavel Machek
Quoted 2 lines
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'
Quoted 46 lines · Jan Engelhardt
Quoted 7 lines · Pavel Machek
Quoted 3 lines
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
_hadareason_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.
Quoted 3 lines
-`J'
Hi,
do man ascii - ESC is 0x1b.
Thats what the esc key should generate - it sometimes echoed as ^[ because the [ = 0x5b
Steve
Signature · 3 lines
"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)
Quoted 4 lines · Stephen Clark
Quoted 3 lines · Jan Engelhardt
It's something between a misdesign and a misconfiguration of the ESC key.
Quoted 8 lines
Quoted 4 lines
In other words, many unices make ESC generate ^[, the general terminal escape character that is _also_ generated by keys like "up", ^[[A.
do man ascii - ESC is
0x1b.
Thats what the esc key should generate - it sometimes echoed as ^[ because the [ =0x5b
Ok I hoped people would be smart enough to figure, but let me rephrase in two ways:
Many unices generate "\x1b" (^[) for ESC, which is also generated by keys like "up", which generates "\x1b[A" (^[[A)
Quoted 4 lines
Quoted 4 lines
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.
And QB generates "\x1b" (^[) while "up" generates "\x00H" (^@H).
Hope this makes things more clear - I interchangably used the ^ and the \
notation. Sorry if that confused anyone.
-`J'
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Jan" == Jan Engelhardt <[email protected]> writes:
Jan> HOWEVER, unix people probably _had a reason_ to make ESC generate Jan> part of what function keys do.
You are looking at it backwards. The Escape key generates an ASCII escape. The funtion keys (including the cursor keys) generate escape sequences because the vt100 won out the title as the most ubiquitous async serial terminal, and linux devs chose to have the console be (mostly) vt100 compatable. As xterm, et al had done before.
The terminals (the actual hardware) used ASCII, so it was normal to use Escape to initiate the sequences used by the function keys.
And that concept goes back a *lot* longer than unix. (Hmm. I can't remember. Did TOPS-20 or its predecessor have glass terminals in the day? I did get to use a DEC paper terminal a couple of times, but that was connected to a VMS box back in the '80s; most of the time it sat in the corner collecting dust....)
At any rate, given that Escape was used to initiate sequences sent to the terminal for funtions such as moving the cursor around the screen, clearing rows or cols, et al it must have only seemed natural to also have it initiate sequences /from/ the terminal which did not fit into standard ASCII. That was after all Escape's purpose in the ASCII std.
If you do want to change the console's terminal emulation, a good first step would be to check whether any existing terminal already uses something other than Escape to initiate function key sequences, and, if so, promote that as the alternative to vt100-esque emulation.
Finally, note that the reason vt100 was chosen for the console was to make it more useful for users who were physically at a linux box, were logged in on the console, and from there logged in to remote servers. That does remain something which the console *must* support.
-JimC
Signature · 1 line
James Cloos <[email protected]> OpenPGP: 1024D/ED7DAEA6
Quoted 33 lines · James Cloos
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
"Jan" == Jan Engelhardt <[email protected]> writes:
Jan> HOWEVER, unix people probably
_hadareason_to make ESC generate Jan> part of what function keys do.You are looking at it backwards. The Escape key generates an ASCII escape. The funtion keys (including the cursor keys) generate escape sequences because the vt100 won out the title as the most ubiquitous async serial terminal, and linux devs chose to have the console be (mostly) vt100 compatable. As xterm, et al had done before.
The terminals (the actual hardware) used ASCII, so it was normal to use Escape to initiate the sequences used by the function keys.
And that concept goes back a *lot* longer than unix. (Hmm. I can't remember. Did TOPS-20 or its predecessor have glass terminals in the day? I did get to use a DEC paper terminal a couple of times, but that was connected to a VMS box back in the '80s; most of the time it sat in the corner collecting dust....)
At any rate, given that Escape was used to initiate sequences sent to the terminal for funtions such as moving the cursor around the screen, clearing rows or cols, et al it must have only seemed natural to also have it initiate sequences /from/ the terminal which did not fit into standard ASCII. That was after all Escape's purpose in the ASCII std.
If you do want to change the console's terminal emulation, a good first step would be to check whether any existing terminal already uses something other than Escape to initiate function key sequences, and, if so, promote that as the alternative to vt100-esque emulation.
Quoted 8 lines
Finally, note that the reason vt100 was chosen for the console was to make it more useful for users who were physically at a linux box, were logged in on the console, and from there logged in to remote servers. That does remain something which the console *must* support.
-JimC
Also ansi came along and pretty much put their blessing on what DEC had done and made the escape sequences a standard.
Steve
Signature · 3 lines
"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)