2) you've got some funky keyboard mapping at the console/GUI
level. This would evidence itself in other editors, so if
you pull up Nano or Emacs and rapidly type "oun" in the same
fashion as you do in Vim, you'd get other funky characters.
How to remedy this lies outside vim...you'd have to check
your keyboard configuration for your console or GUI/WM
For the moment it looks like option two, then again my
keyboard is has had so much caffeine spilt on it, it might be
in a slightly altered state of mind. Nonetheless, the problem
is not peculiar to vim, and thus not Vim's problem. Thanks for
the tip off...
Glad to help point you in the right direction. You might try
booting off a generic live-CD that would have fairly standard kbd
mappings. Pulling up a shell, you can then use
bash$ xev > ~/keylog_live.txt
when the window pops up, you can rapidly type your "oun", then
close the window. You should have a list of all events that
fired. If you mount your HDD and copy this file to a place you
can find it on your machine, reboot, and then perform the same
sort of action within your native configuration (into
"keylog_native.txt"), you should be able to diff them ("diff
keylog_live.txt keylog_native.txt") and see if your local
configuration is doing anything funky.
You might also have some tool for checking/changing your keyboard
mapping. It could be that you're configured for some
international mapping with dead-keys or at least things in places
your keyboard doesn't have labeled. :)
Alternatively, if you've just got another kbd floating around the
house (if, IIRC, you said you're running Gentoo--that's usually
indicative of the type of person likely to have >1 kbd around the
house... ;) you can try swapping it out to see if it's hardware
or software related.
Just a few more ideas,
-tim
