Richard Pöttler <[email protected]> writes: > Hi, > > I like to try out vimscripts, to test, whether they help me with my > editing. After a while I lost oversight of all my installed scripts and > their current status. Trying to track them with git, which didn't help > much, so I hacked together a perl script to do this job. > > Since writing a script for me alone doesn't make much sense, I decided > to give you a short note, if you experience the same problem. > > The script can be found at [1] with a little description. If you are > only interessted in the plain script, fetch the latest version from [2]. > If there is something missing, you can create a ticket at [3]. To start > of, simply execute the script and type "help".
Apparently at least some of the packages called in the lengthy list of `use X;' Or `use feature X; Are not part of a standard perl install. I have quite a few non default perl packages installed... but here your script blows up looking for `feature.pm' if I type. vimscripts.pl help Further... perldoc fails to find: Archive::Extract; Config::General File::Fetch On my system as well. So to even test your script.. I'd need to install whatever use Feature[...] is calling. And Archive::Extract, Config::General and File::Fetch. I think that means lots of folks will pass on trying to test or use your script. Too bad, too because it looks like you put a fair bit of effort into it. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
