Re: UTF-8 and Alt key in the console

["John T." <j.thomast@yahoo.com>]

--- "H. Peter Anvin" <hpa@zytor.com> wrote:

> John T. wrote:
> > 
> > That's because you are working in "meta sends ESC" mode.
> > Although this is OK for most applications, for some it isn't.
> > Thus there have always been two modes, "meta sends ESC"
> > and "meta sets 8th bit". (toggled with setmetamode on the
> > console)
> > 
> > Vim relies on "meta sets 8th bit". Unfortunatelly the code
> > for this options does not work in UTF-8 in the console. What
> > I'd like to do is make this a viable option in UTF-8.
> > 
> 
> No, fix vim instead.
> 
> "Meta sets 8th bit" is so obviously and totally broken, since it maps 
> onto real characters, and has been doing so for at least 20 years. 
> Meta-L maps onto LATIN CAPITAL LETTER I WITH GRAVE, both in 8-bit mode 
> and in your proposed UTF-8 mode.  It just becomes even more obvious how 
> unbelievably broken it is when you try to map it onto UTF-8.
> 
> Seriously, fix the crap.
> 
> 	-hpa
> 

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.


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ