Matthew Desjardins wrote:
> There have been a couple of people posting about how the new package
> feature can, in its current state, replace Pathogen.
>
> https://groups.google.com/d/msg/vim_dev/BN5DuHpzzBc/OjoGDSqeEQAJ
> https://groups.google.com/d/msg/vim_use/QHqDKtdqUkk/PY7WydFdAQAJ
>
> Could someone explain how? It doesn't seem to work for plugins that
> don't have a "plugin" directory, and as far as I can tell from the
> source it's not supposed to, either.
>
> Why was this decision made to only support plugins with a "plugin"
> directory?
It's very easy to add an empty plugin/foo.vim file. If you really need
to, I would expect nearly every plugin to at least do something, such as
defining a user command or mapping. Maybe it's empty if you only want to
make a syntax file available.
It would be possible to make another command than :loadplugin to find
any directory with the specified name under 'packpath', but I don't see
a good reason. Perhaps adding a remark to the documentation is
sufficient?
--
A special law prohibits unmarried women from parachuting on Sunday or she
shall risk arrest, fine, and/or jailing.
[real standing law in Florida, United States of America]
/// 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_use" 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_use" 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.
