From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: "John T." <j.thomast@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: UTF-8 and Alt key in the console
Date: Fri, 28 Mar 2008 16:26:53 -0700 [thread overview]
Message-ID: <47ED7EBD.8070009@zytor.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0803231942380.3157@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
>>> The best probably would be to introduce an escape code, along the lines
>>> of other escape codes in the terminal interfae.
>>
>> You're right.
>>
>> Many say Unix is also broken compared to Plan 9.. sometimes it's
>> too late. The real fix for this issue seems like it'd be very
>> hard to accomplish.
>
> The idea of revamping the escape codes is not all that bad.
>
> Thanks to terminfo, this should be easy. Change vt.c,
> add corresponding terminfo entry and set TERM to something
> that has not previously existed.
>
> About the ESC key, I thought, would it suffice to replace its
> current output of ^[ with ^[^[?
It would be better to assign a CSI (ESC [) code to it, like other
function keys. Unfortunately, the terminal everyone tries to emulate
(Linux does so quite poorly due to its broken implementation of ISO
2022, but that's less of an issue with UTF-8), VT 220, had ESC on the
F11 key, so the CSI 2 3 ~ sequence it uses we use for the F11 key.
Doesn't mean we can't assign another one.
One would also like to distinguish, say, Backspace from Ctrl-H. This is
trickier, because the termios settings don't permit compound keys. The
most obvious way to deal with that is an escape code for Ctrl-H, but
that has the risk of breaking a lot of other things.
-hpa
next prev parent reply other threads:[~2008-03-28 23:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 15:15 UTF-8 and Alt key in the console John T.
2008-03-23 15:29 ` Jan Engelhardt
2008-03-23 15:46 ` John T.
2008-03-23 16:54 ` H. Peter Anvin
2008-03-23 17:47 ` John T.
2008-03-23 17:55 ` H. Peter Anvin
2008-03-23 18:13 ` John T.
2008-03-23 18:46 ` Jan Engelhardt
2008-03-28 23:26 ` H. Peter Anvin [this message]
2008-03-29 0:07 ` Jan Engelhardt
2008-03-29 0:23 ` H. Peter Anvin
2008-03-29 0:44 ` Jan Engelhardt
2008-03-29 1:07 ` H. Peter Anvin
2008-03-29 6:33 ` David Newall
2008-03-29 17:05 ` H. Peter Anvin
2008-04-01 20:13 ` Jan Engelhardt
2008-04-01 20:22 ` H. Peter Anvin
2008-04-02 0:02 ` David Newall
2008-04-02 0:38 ` H. Peter Anvin
2008-04-06 8:46 ` Marko Macek
2008-04-06 10:14 ` David Newall
2008-04-06 16:37 ` H. Peter Anvin
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=47ED7EBD.8070009@zytor.com \
--to=hpa@zytor.com \
--cc=j.thomast@yahoo.com \
--cc=jengelh@computergmbh.de \
--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.