From: "John T." <j.thomast@yahoo.com>
To: "H. Peter Anvin" <hpa@zytor.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 11:13:55 -0700 (PDT) [thread overview]
Message-ID: <205509.99433.qm@web45710.mail.sp1.yahoo.com> (raw)
In-Reply-To: <47E69974.5000208@zytor.com>
--- "H. Peter Anvin" <hpa@zytor.com> wrote:
> 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.
There's always the "timeout" hack. It is allright with the
arrow and function keys because the second character in these
cases (`[' usually) is not a commonly typed vim command.
> That being said, quite frankly, *both* Meta key conventions are
> incredibly broken.
Indeed, I agree with you here.
> 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.
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. In the meantime, maybe we could do this easy
fix. Or not. But we have a situation.
> -hpa
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
next prev parent reply other threads:[~2008-03-23 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 15:15 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. [this message]
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=205509.99433.qm@web45710.mail.sp1.yahoo.com \
--to=j.thomast@yahoo.com \
--cc=hpa@zytor.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
all inboxes | Powered by JetHome®