On 28/08/09 17:55, Matt Wozniski wrote:
[...]
> No, you understood my advice. I'm not terribly well-schooled in
> international keyboard layouts, but I would be surprised if there
> wasn't a qwertz layout without dead keys... Composing keys are much
> more convenient than dead keys when programming anyway, imho, and it
> would be quite odd if MS didn't make that configurable. Maybe Tony M
> can weigh in about that; it's probably a question that he knows the
> answer to.
I don't know much about various keyboard layouts; the one I use (Belgian
AZERTY) has a lot of dead keys, and I love them. But yes, as you say
below, the translation between what you press and what Vim gets is at
the lowest level, and Vim mappings (if any) come after that. When you
hit a dead key, Vim gets nothing yet; the "transformed" character is
sent once you hit the next key after the dead key, so Vim can't
intervene between the two (except, maybe by getting out of the Vim world
with system(), libcall(), etc.). So yes, the solution (if any) should be
at the OS level, not at the Vim level.
>
> But basically, my entire point is that the dead key magic takes place
> at a much lower level than vim can access, so there's no way you could
> change the behavior with a vimscript (except for possibly by hacking
> together some Deep Magic using libcallnr() and a self-written DLL or
> some such). If I were the OP, I'd spend my time searching google for
> general answers to disabling dead keys in windows, and not try to look
> for anything specific to a single program.
>
> ~Matt
Best regards,
Tony.
--
THE LESSER-KNOWN PROGRAMMING LANGUAGES #12: LITHP
This otherwise unremarkable language is distinguished by the absence of
an "S" in its character set; users must substitute "TH". LITHP is said
to be useful in protheththing lithtth.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
