Hey Tony, > Does any of these scripts check whether it has already been run?
I don't believe so. All the scripts worked fine prior to applying this patch with the runtimepath set as I mentioned. > For any one which does, is there a script of the same name at the same > relative location in $VIMRUNTIME? No. > If there is, you should place that directory early in 'runtimepath'. Normally > the default value ought to be OK: on Windows, > > ~/vimfiles,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/vimfiles/after > > Any nonexistent directories in the list are treated as empty anyway. The reason I set runtimepath as I did is because I run both a native gVim (compiled via MinGW) as well as cygwin vim (compiled via cygwin). I've configured cygwin to use the windows home directories (C:\Documents and Settings\<user ID>) as opposed to the standard C:\Cygwin\home. This allows for a common vim user configuration environment in both environments. Cheers! Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
