> The purpose of this project is to create stable functions to return values > or to execute actions. > A sample directory structure could be: > > autoload/lib > autoload/util > autoload/buffer > autoload/cmdline > autoload/time > ... > > Sample functions/scripts: > > autoload/lib/filelist > autoload/util/scratch > autoload/buffer/bufferlist > autoload/cmdline/removelastpathcomponent > autoload/time/weekday > ... > > A developer that wants to utilize such a function, should include on the > top of the implementation, a standard code block to request the function. ...
Hmmmm... rings a bell. Are you modeling this after the Perl CPAN module structure (search.cpan.org)? That setup is obviously very successful. Looking at the differences of perl and vim, I have a few thoughts: 1.) The "use lib..." structure in perl is built into the language, and vim does not have an equivalent. Perhaps this would be a good, straightforward feature to add to the next version of vim? 2.) "The purpose of this project is to create stable functions to return values or to execute actions." That leaves out much of the valuable brainwork on vim.org, since many of the scripts in vim are meant to be self-contained, the user only needs a macro (usually) to start the script. Can we think of a way to include those as well? 3.) Chip Campbell's GetLatestVimScripts plugin should be leveraged. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
