On 26/02/09 23:00, Ingo Karkat wrote: [...] > So in the spirit of sharing and learning from each other that you've so > graciously started, let me reciprocate with one of my scripts that I use to > detect old VIM versions and then source archived plugin versions that still > support that VIM version.
:-) Wow! Nice script. > (It seems that you're going out of your way to support > old versions; not all plugin authors are so diligent.) > > -- best regards, ingo > My interest in portability dates from the time when I had a double-boot or even triple-boot box and tried to use the same vimrc on Windows, RedHat and SuSE. I quickly noticed that the 'guifont' option was not compatible, which led me to some research and writing the VimTip which has now become http://vim.wikia.com/wiki/Setting_the_font_in_the_GUI . Later I noticed that (on a SuSE-Linux-only box) I had not only the latest Vim (7.0 then, own-compiled, and first in the $PATH) but also gvim 6.4, vim 6.4 and kvim 6.1 from SuSE, as prerequisites for several other packages (and therefore not to be uninstalled). Of course I wanted my .vimrc to work with no errors in all of them. SuSE has (belatedly) dropped distribution of kvim since them, but even though my "day-to-day all-purpose editor" is a huge gvim version, I also build a "minimum" version with tiny features, no GUI and the executable name "vi", to check that my vimrc and Bram's runtime files are portable over the full range of featuresets. (As a side advantage, it overrides the Vim version (if any) distributed with package vim-minimal by coming before it in the $PATH.) Best regards, Tony. -- Even if you do learn to speak correct English, whom are you going to speak it to? -- Clarence Darrow --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
