>> Personally, I find external-to-Vim methods for entering Unicode characters >> to be much better. For example, in order to get what I think your arrow is >> (=>) in all X11 programs (including Vim under a terminal emulator and Gvim), >> by typing <Compose> + <equal> + <equal> + <greater-than> (where <Compose> = >> <CapsLock>), I can add this line to ~/.XCompose: >> >> <equal> <equal> <greater> : => >> >> Granted, it's less portable (in terms of non-X11 environments), and can be a >> pain to set up initially, but it's worth the effort if you find yourself >> using non-keyboard characters frequently. > > Excellent idea. I do use compose keys but never thought about adding my own. > Thanks.
After experimenting with ~/.XCompose I find that it is not an ideal solution, but perhaps only because I don't know how to use it properly. The main problem I'm having now is that different programs behave differently if two sequences have a common prefix. For example, suppose I want: <Multi_key> <less> <equal> <greater> : "⇔" # logical bi-implication but also want <Multi_key> <less> <equal> : "≤" # less-than or equal to Then it seems like xterm picks the first one, and I don't know what to press after the <equal> to say "stop the sequence here", and gvim picks the second without giving me a chance to put the <greater> in. An overarching problem is that I cannot find any documentation on how the ~/.XCompose file should be written, and how compose keys work in general, apart from random forum/mailing list posts. Is there any official X documentation (that has eluded me)? -- 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
