Hi Gene, et al.,
Please see my comments below.
On Tue, Jun 06, 2006 at 03:49 PM PDT, Gene Kwiecinski wrote:
... Text Deleted ...
GK> >Here's a sample of what I get when I type each letter in the English
GK> >alphabet twice in a row (e.g.: aabbccddeeff...):
GK>
GK> >abbcdeffgghijjkklmmnopqqrßtuvvww×yzz
GK> > ^
GK> > |
GK> > this is the greek Beta character (in case it
GK> > got lost in the transmission)
GK>
GK> >Notice how some characters only show up once, and the one greek
GK> >character.
GK>
GK> Aha! That "beta" is actually a German "SS", "ß" ("sz" ligature) iirr.
GK>
GK> The 'X' is a math times ("×" no?).
GK>
GK> All the other (usually) vowels have similar "compounding", eg,
GK> [aeiou] with accents of various types (try typing "a'" or "a:",
GK> ferinstance), Polish "l/" (slashed-ell, don't know the sgml entity
GK> offhand), Spanish "n~" (en-tilde, "ñ"), and so on.
Very interesting observation!
It turns out that if I enter any of the English vowels (a-e-i-o-u or y)
as the first character of the search, it will show up. But if it's not
the first char entered, it becomes part of a multi-byte char.
Here are the results of the keystrokes you suggested to try--and a few
more:
Typed | Result
------+--------
a' | á <- when "a" is not the first char typed
a: | ä <- when "a" is not the first char typed
e' | é <- when "e" is not the first char typed
e: | ë <- when "e" is not the first char typed
l/ | / <- when "l" is not the first char typed
|
~n~ | ~ñ <- Note the first time the char is entered it is echoed "correctly"
~~n | ~ñ <- Note the first time the char is entered it is echoed "correctly"
nn~ | nñ <- Note the first time the char is entered it is echoed "correctly"
n~n | nñ <- Note the first time the char is entered it is echoed "correctly"
GK> Try some funky combinations like "l/", "n~", etc., and see what pops up.
GK>
GK> If this is the case, then I don't *think* it's an issue with 'vim',
GK> but something with the GTK1 compile, that maybe it includes as a
GK> "bonus" some cooked keystroke editing to be able to easily get
GK> weirdo characters right from the keyboard for functions like getc(),
GK> scanf(), etc.
GK>
GK> We may be on to something now... :D
I hope so. But I still wonder why I only see this behavior on the
search line; and I don't see it when the respective char is the first
one typed. And there's the apparent correlation with incsearch and
laststatus. I feel my migraine coming back ;)
--
Mun
