On Monday, December 9, 2013 2:55:07 PM UTC-5, Charles Campbell wrote: >Paul wrote: >> I want to set cursorline when netrw is open, but when I open a file >> by either pressing "o" or <CR>, I don't want the activated >> cusorline to be inheritted in the open file (which often happens). >> I've ensured that cursorline is activated in netrw using setl, and >> I confirmed that cursorline should otherwise be off via: >> >> set cursorline? (outside of netrw) setg cursorline? >> >> I originally had "setl cursorline" in >> vimfiles/after/ftplugin/netrw.vim. This did not prevent file from >> opening with cursorline set, so I tried "setl nocursorline" in >> vimfiles/after/ftplugin/netrw.vim and "setl cursorline" in >> vimfiles/before/ftplugin/netrw.vim. (I know, there doesn't seem to >> be any formalized role for a before directory, but I thought it >> wouldn't hurt to try). This doesn't seem to do it either. >> >> Is there a surefire way to ensure that cursorline activation is not >> inheritted from netrw when a file is opened from netrw? > > Nothing is surefire; but perhaps v150l of netrw will help (see > http://www.drchip.org/astronaut/vim/index.html#NETRW).
Thanks, Charles. I definitely keep that in mind. At my shop, though, I'm pretty well stuck with vim 7.3 up to patch 46. -- -- 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/groups/opt_out.
