From: "H. Peter Anvin" <hpa@zytor.com>
To: "John T." <j.thomast@yahoo.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>, linux-kernel@vger.kernel.org
Subject: Re: UTF-8 and Alt key in the console
Date: Sun, 23 Mar 2008 10:55:00 -0700 [thread overview]
Message-ID: <47E69974.5000208@zytor.com> (raw)
In-Reply-To: <578664.95535.qm@web45709.mail.sp1.yahoo.com>
John T. wrote:
>
> OK, let's see if I can answer this.
>
> Vi has 32 years of ESC key use tradition which doesn't play
> well with "meta sends ESC".
>
> Even though "meta sets 8th bit" is "broken" in your point-of-view,
> that didn't stop it from being used all these years. The fact
> that it maps into real characters is not a problem if you can just
> use a CTRL-V equivalent in bash or vim.
>
> Furthermore, it is an _option_. No one is obliged to use it.
> So it's a question of:
>
> .. _forcing_ the end of "meta sets 8th bit"
> .. leaving things the way they are, and have them keep working,
> as xterm did.
>
> So guess we should fix xterm too?
>
> I think you're exagerating.
>
Hardly. vim clearly can deal with the ESC-is-prefix issue anyway, since
otherwise it wouldn't be able to use arrow keys.
That being said, quite frankly, *both* Meta key conventions are
incredibly broken.
What I would much prefer is to see would be a brand new convention where
different keys (Ctrl, Meta, Super, Hyper, Alt or even in some cases
Shift) issues a unique prefix which doesn't conflict with anything else.
Emacs has tried to promote such a convention of the format
<CAN> @ <bucky> <keystroke> which is a lot better, although it's a bit
Emacs-centric (using <CAN> / ^X as the initial character is not really a
very good choice.)
The best probably would be to introduce an escape code, along the lines
of other escape codes in the terminal interfae.
-hpa
next prev parent reply other threads:[~2008-03-23 17:55 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 [this message]
2008-03-23 18:13 ` John T.
2008-03-23 18:46 ` Jan Engelhardt
2008-03-28 23:26 ` H. Peter Anvin
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=47E69974.5000208@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).