linux-kernel - Re: UTF-8 and Alt key in the console

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Mar 2008 11:13:55 -0700 (PDT)
From:	"John T." <j.thomast@...oo.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	linux-kernel@...r.kernel.org
Subject: Re: UTF-8 and Alt key in the console


--- "H. Peter Anvin" <hpa@...or.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/