On Feb 6, 3:55 pm, Matt Wozniski <[email protected]> wrote: > On Sat, Feb 6, 2010 at 1:50 PM, Girish Venkatasubramanian wrote:
*snip* > > To help this, I am considering mapping j and k (or the arrow keys) to > > gj and gk so that the scrolling happens from one line to the next > > virtual line and not from to the next actual line. > > 1) My first choice is remapping the arrow keys? Is this a bad idea? > > Should I rempa only for specific modes? > > I think it's perfectly reasonable to map the arrow keys to do > something slightly different than j/k. Obviously, you'd only want > that remap in normal, visual, and operator-pending modes, though. You > don't want pressing <Down> in insert mode to insert "gj" into the > buffer at the cursor. So, the command would be > > :noremap <Down> gj > :noremap <Up> gk Thanks. Those did the trick > *snip* > I'm not sure what the problem with this is? That sounds like exactly > what gq is supposed to do. I should have explained this a little better. I do realize that this is fo and gq's behavior. What I would like to happen on gq is Introduction This is a comment. This is another comment But I realize that is asking a bit too much. I cant expect Vim to distinguish between carriage returns depending on what *I feel* should happen. Same way, I cant expect vim to distinguish between comments and commented out code, as you rightly point out. So let me rephrase these *problems* as features that I tried out but did not like very much. It may even be an issue of my not being used to this feature and it may take some time to understand and appreciate it. *snip* > In the future, please bottom post on this mailing list; it's list policy. Will do that. Thanks for letting me know about the policy. > > ~Matt -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
