Overriding builtin plugin with packages?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Overriding builtin plugin with packages?

Ben Fritz
In testing my 2html plugin, I wanted to install it simply in my user directory using the packages feature, like I do with my other plugins.

When I do this, placing a vim-tohtml folder under .vim/pack/mine/start/vim-tohtml, Vim correctly adds the vim-tohtml package directory to the runtimepath, prior to the built-in runtime.

However, the plugin file in vim-tohtml runs *after* the plugin file from the distribution files for some reason, which prevents it from loading.

Is this intentional?

I do have a workaround: I add vim-tohtml to the "opt" tree instead, and place a "packadd vim-tohtml" in my vimrc. But I thought it was weird that is required.

What other workarounds are usable for this? Anything better?

--
--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Overriding builtin plugin with packages?

Bram Moolenaar

Ben Fritz wrote:

> In testing my 2html plugin, I wanted to install it simply in my user
> directory using the packages feature, like I do with my other plugins.
>
> When I do this, placing a vim-tohtml folder under
> .vim/pack/mine/start/vim-tohtml, Vim correctly adds the vim-tohtml
> package directory to the runtimepath, prior to the built-in runtime.
>
> However, the plugin file in vim-tohtml runs *after* the plugin file
> from the distribution files for some reason, which prevents it from
> loading.
>
> Is this intentional?

Yes.

> I do have a workaround: I add vim-tohtml to the "opt" tree instead,
> and place a "packadd vim-tohtml" in my vimrc. But I thought it was
> weird that is required.
>
> What other workarounds are usable for this? Anything better?

You can execute :packloadall in your .vimrc.

--
THEOREM: VI is perfect.
PROOF: VI in roman numerals is 6.  The natural numbers < 6 which divide 6 are
1, 2, and 3. 1+2+3 = 6.  So 6 is a perfect number.  Therefore, VI is perfect.
QED
                                                    -- Arthur Tateishi

 /// Bram Moolenaar -- [hidden email] -- 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 [hidden email].
For more options, visit https://groups.google.com/d/optout.