Nazri Ramliy wrote: > On Wed, Sep 10, 2014 at 11:58 PM, 0xBADDCAFE <[email protected]> wrote: > > Nowadays modern plugin managers add many runtimepath that contain scripts. > > These path strings can be over 1024 bytes easily. > > Perhaps a new option would be better, 'runtimedir' - all directory found in > there are regarded as individual runtimepath elements. This would make giant, > unreadable 'runtimepath' values go away. glob() can help achieving > deterministic addon loading order, so we can prefix the directory names in > 'runtimedir' with numbers to enforce ordering if necessary. > > Those who are familiar with apache2 would notice the similarity of > enabling/disabling modules by making a symlink from one directory to another.
Although removing arbitrary limits is good, making 'runtimepath' very long is a bad idea. Every time Vim searches for a runtime file it will visit those directories and request the contents. A plugin manager better use another mechanism. A dictionary to lookup what file is located where is a LOT faster. -- Would you care for a drink? I mean, if it were, like, disabled and you had to look after it? /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
