Tony Mechelynck <[email protected]> writes: >>> As a brute-force way to determine which of the scripts sourced after >>> your vimrc is disabling highlighting, you could move them all out of the >>> plugins directory temporarily, verify that syntax highlighting remains >>> enabled after your vimrc is sourced at startup, then move the global >>> plugins back in a few at a time, starting vim each time, until you've >>> zeroed in on the offending script. >> >> If you don't want to move the plugin scripts around, you could do >> something like this... >> find ~/.vim/plugins /usr/local/share/vim/vim72/plugin/ -iname >> '*.vim'|xargs grep 'let[[:space:]]\+\(g:\)\?loaded_' >> >> And start adding lines to the top of your .vimrc to set the various >> g:loaded_<...> vars (to prevent the plugin from loading) until things >> start working. Of course, you would need to use the path or paths >> appropriate to your system. You might try checking only the >> non-distributed plugins first, as the most likely candidates.
Thanks, the machine is down for a day or two so can't really investigate right now. If I start vim with no .vimrc is there some default highlighting I should see? --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
