On Sep 7, 9:44 am, Taylor Hedberg <[email protected]> wrote: > > then the syntax highlighting is fine. The only difference in the output > of `:scriptnames` between these two test cases is the inclusion of > $VIMRUNTIME/plugin/netrwPlugin.vim in the netrw case, so again, it seems > that netrw is somehow the culprit. >
Are you sure this is the only difference? stuff in $VIMRUNTIME/plugin is normally sourced automatically whenever you load Vim, regardless of what you do in Vim, unless you've turned plugins off from a command- line option or the 'noloadplugins' option. > One other thing I tried was to edit the file with netrw and then save it > locally with `:saveas`. After doing this, the syntax problems remained, > but once I exited Vim and reopened the local copy of the file, the > problems went away. > How about trying editing the local file with netrw? I would expect it to misbehave in the same way if netrw is the culprit. I don't think you mentioned, did you verify that the correct filetype is set for both methods of editing? Maybe netrw is interfering with filetype detection. What version of netrw are you using (check the header info in the plugin files)? What version of Vim? What compiled feature set? -- 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
