First, Stephen, please don't top-post. Like it or not (and personally I don't!) that is the convention on this list. I must admit, though, that particularly after somebody else has already bottom-posted, top-posting makes things a big mess. In future, please write your replies under short, relevant extracts of the mail you are replying to.
Therefore I propose letting users choose their preferred keyboard layouts instead of forcing any specific one to them.
Sorry, but this is not what we are discussing. Vim already has this functionality. As you discovered, it can work through what it calls 'keymaps' (:help keymap). It also works with a number of different input methods on different platforms, particularly when using Gvim.
Maybe a step forward to change the layout on-the-fly by the following command (when changing keyboard setting in X window system): :set keyboardlayout=...
And there is even better than this already: Vim's 'iminsert' option (:help iminsert). Of course, you can write mappings (as I have done) to change the 'keymap' option between values, too.
and there would be 4 files: QWERTYsequence.vim QWERTZsequence.vim QWERTYstructured.vim QWERTZstructured.vim
You are miles ahead of us, Stephen! It is indeed possible that this kind of thing could evolve. In fact, the functionality for this part of it is already there. What we need, though, is a way to get the structured kepress information into vim in the first place, so that keymaps (and more importantly, mappings) can refer to them. Mappings are more important, because what we are discussing isn't really about text input, but about shortcut keys. At the moment, Vim sometimes can't tell the difference between Tab and Control-I (and a lot of other things). And because Vim sometimes has no way of telling the difference, at the moment, it doesn't even bother to notice the difference when it *can* tell. We want to change that. After we have changed that, then your idea of having multiple keyboard layouts, some for when these keys can be differentiated, and some for when they cannot, may become useful. I hope we won't need that idea, though, but will be able to write one keymap file that works well in both situations. But that is for later. First we need to get all the keys recognised as properly as possible. Ben. -- You received this message from the "vim_dev" 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
