Raúl wrote: "The usage pattern you explained in your message doesn't make sense as a mode for me, because those actions belong to "normal" mode."
I'm no psychologist, but I think my mind is modal - with more modes than vim. Sometimes I want to browse files, then I'm in a 'browse- file' state of mind, and want to use a browse mode. Sometimes I want to write loads of text, and I'm in an according state of mind, and I want to use insert mode. Sometimes I want to edit (rather than really create) text, and want to use a different insert mode. And if I have a (tab separated) table in my text, again another mode would be useful. "I suppose that the OP knows that mappings can solve his problem, but nonetheless he was interested in adding new modes (which, in the end, would make available plenty of "ordinary" keys, one set for each new mode). The key here is not if "Insert mode" is a mode or not, or if mappings can solve OP's problem. The key here is, IMHO, is a good idea to add new modes for certain operations (like moving between windows, etc.)." Indeed! Not having to press Ctrl's and not having to move away from the keyboard (as with F's) would be much faster. "If you make just one move... well, then the "mode" is already there" Yes, but in that mode I would also have keys for switching between buffers and for scrolling in that mode, and maybe for following links. "The problem is: how do you go to that mode?" I think that's the biggest problem: finding an unused key in normal mode. That can be used as a leader, followed by a (programmable) mode specifier. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
