On Monday, October 28, 2013 12:00:40 AM UTC-5, Andre Sihera wrote: > On 28/10/13 02:58, Paul LeoNerd Evans wrote: > > >> Please explain how you are going to differentiate CTRL-I and Tab in > > >> > random terminal emulator. Some may be configured to output either as > > >> > CSI sequence, but not all. This is not simply historical artifact. > > > You can't. Does that matter? Some people write a :map from F12, but > > > some terminals lack an F12 key. Vim has no problem storing maps from > > > keys it knows the terminal cannot possibly generate. If users are > > > mapping from keys their terminal cannot type that is their problem. > > > > > I'll tell you what the real problem is. It's bare-faced arrogance like > > this that all users who don't fit into the ideas of the vocal few > > "obviously" have a problem. > >
I think he's saying that if your terminal cannot tell a <C-I> from a <Tab>, then neither will Vim be able to. And that if a user tries mapping them separately but the terminal cannot actually send a <Tab> that differs from <C-I> then it is the user's fault for using a dumb terminal while trying to use this feature in Vim. > > I'll tell you one good reason why people are mapping keys from > > their terminal that that cannot physically type, and that is keyboard > > remote control (synergy, virtual machine environments, etc.). > > I, for one, have all my F-keys mapped up onto other keys because > > the host system I am using to remote control intercepts all the F- > > keys before they get passed onto the remote system, so I have to > > map them up. > > And you'll be able to continue doing this. Nobody is suggesting removing the ability to: :nmap <A-F>1 <F1> :nmap <A-F>2 <F2> etc. (or the reverse, I'm not 100% sure what you mean by "map them up") What is being suggested is that you could do: :nnore <Tab> :echo "hello"<CR> :nnore <C-I> :echo "world"<CR> If you want <C-I> and <Tab> to do the same thing, then do this instead: :nmap <C-I> <Tab> or this: :nnore <C-I> :DoSomething<CR> :nnore <Tab> :DoSomething<CR> > > Additionally, TAB, for example, in Japan can be a language input > > modifier key for switching between kanji/kana and Roman alphabet. > > Some keyboards have an additional dedicated key for this but not > > all do. On a remote link you may have to use Ctrl+I to get a tab > > character to come out as the tab key locally can be intercepted at > > a very low level by Japanese (or other foreign) operating systems. > > > > I do not believe I am the only one who uses keyboard/mouse remote > > control to another system and edits a file in ViM, nor am I the only > > one who uses a computer in more than one language and uses VIM > > keyboard mappings to circumvent local system inadequacies with > > regards to multi-lingual support. However, as I guarantee that most > > of these other people don't "hang out" on "#vim" for most of their > > lives I take the view that the "vast majority" of ViM users (including > > myself) would be annoyed if their keyboard mappings just suddenly > > stopped working because of a few who can't see beyond their English- > > only QWERTY-compliant wire-connected keyboards. I'm not sure whether there are more people surprised by the inability to map <C-I> separate from <Tab>, or whether there are more that would be frustrated that they must now manually map <C-I> to <Tab>. But I do know the first seems more logical to fix than the second. Since the second is the current behavior, then I suppose I'd support either having an option to turn this on (probably part of cpoptions), or better, falling back to the current behavior if no mappings exist. And yes, I mean NO mappings (of that synonymous pair). Because if you define a mapping for <Tab> and want <C-I> to trigger it, you could define a second <C-I> mapping in the same place. But if you want to keep the default behavior of <Tab> and still want to map <C-I> to something, you should not need to use two mappings to accomplish that. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
