On 15/06/10 21:46, William Fugy wrote:
Thanks, i seems to know what's happening. However, why vim(or
Windows?) doesn't make a mapping as follow?
ASCII-----------------Latin1
Ctrl+0x20 -------> 0x80
Ctrl+0x21 -------> 0x81
...........
Ctrl+0x3F -------> 0x9F
And if so, both Ctrl+digit and Alt+digit can work.
Is 0x80~0x9F occupied by Ctrl+Alt+'x'?
Regards,
-William
I don't know what Window does -- some programs want to treat Ctrl-I as
other than Tab, Ctrl-M as other than Enter, etc. -- but Vim simply
follows what was set long ago by ASCII (at a time when 7 bits were
thought to be enough for a character and anything happening outside the
borders of the 50 states, and also anything in non-English languages
including Spanish, Yiddish, Cajun and Cherokee, could just as well have
been in outer space), and it leaves, among others, Ctrl+0x20 to
Ctrl+0x3F "undefined".
And yes, Ctrl+Alt+@ is 0x80, Ctrl+Alt+A is 0x81, etc. (in UTF-8 or
Latin1, these 32 characters, 0x80 to 0x9F, are all rarely used
non-printing control characters; in Latin9 aka ISO-8859-15 and in
Windows-1252 some or all of these byte values were attributed to
characters nonexistent in Latin1, and above U+00FF in Unicode, such as
the Euro sign, the French oe and OE digraphs, etc.).
***
*** REMINDER: bottom-posting is the custom in the Vim groups.
*** In other groups, well, "in Rome, do as the Romans do".
***
Best regards,
Tony.
--
"In any world menu, Canada must be considered the vichyssoise of
nations -- it's cold, half-French, and difficult to stir."
-- Stuart Keate
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
