On Wednesday, January 14, 2015 at 5:20:15 AM UTC-5, John Little wrote: > I see it with netrw153. > > In autoload/netrw.vim, the NetrwLocalRm function takes a range, firstline to > lastline. It loops through the range: > > let ctr = a:firstline > while ctr <= a:lastline > exe "NetrwKeepj ".ctr > > This sets the cursor to the first non-blank character of the line, if the > 'startofline' option is on (which is the default) and so the following call > to NetrwGetWord finds the word at the beginning of the line. > > I imagine Dr Chip uses nostartofline. If I set nosol in my .vimrc, the > problem does not occur. > > Regards, John Little
John, excellent diagnosis! Setting nosol resolves the issue -- although I'm worried it may impact behavior elsewhere? As startofline defaults to being on, perhaps it's best to work around this issue with an autocmd? I've tried the following: autocmd FileType netrw setlocal nostartofline autocmd FileType netrw autocmd BufRead,BufEnter <buffer> setlocal nostartofline While they work and set nosol in the netrw buffer, it seems that the nostartofline option persists outside the netrw buffer itself. I'm a new vim user && still feeling myself around -- appreciate any help I can get. ~ Brice -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" 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/d/optout.
