On Jul 25, 10:15 am, at <[email protected]> wrote: > If I do this: > 1. Start gvim > 2. :e test.f90 > Then I get messed up syntax highlighting... > However, if I do this: > 1. Create a file called test.f90 > 2. Double click on it in my OS so that it opens in gvim > Then the syntax highlighting is perfect.
Sounds like you've got two versions of gvim, and the version invoked by the file association is different from that invoked by the gvim command. Try running :ver in both cases. I get in this mess with Windows every time the vim version changes, because the file associations in the registry have the full path in them. I end up hacking the registry with vim-generated .reg files, thinking there must be a better way. How is one supposed to cleanly move from one vim version to another in Windows? John --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
