Re: standard way include plugin as a dependency of another plugin

2017-08-01 Thread Luc Hermitte
I've made a small (pathname) error in my answer, see the correction below. - Mail original - > De: "Luc Hermitte" <hermi...@free.fr> > À: "vim use" <vim_use@googlegroups.com> > Envoyé: Mardi 1 Août 2017 13:33:17 > Objet: Re: standard way incl

Re: standard way include plugin as a dependency of another plugin

2017-08-01 Thread Luc Hermitte
Hi, (Sorry, it seems I've deleted the original message, and I'm not answering to the mail I should be answering to). > On 30/07/2017 04:40, sash...@gmail.com wrote: > > I'm writing a plugin and want it to depend on another plugin > > installed. At the moment I just have a line > > > > source

Re: standard way include plugin as a dependency of another plugin

2017-08-01 Thread lith
> I'm writing a plugin and want it to depend on another plugin installed. At > the moment I just have a line > > source I sometimes use something like this: if !exists('g:loaded_DEPENDENCY') || g:loaded_DEPENDENCY < 100 runtime plugin/DEPENDENCY.vim if

Re: standard way include plugin as a dependency of another plugin

2017-07-30 Thread Lifepillar
On 30/07/2017 04:40, sash...@gmail.com wrote: Hi I'm writing a plugin and want it to depend on another plugin installed. At the moment I just have a line source in my plugin that pulls in that plugin. Is there a standard way of doing this or do plugin authors just invent their own way?

standard way include plugin as a dependency of another plugin

2017-07-29 Thread sash...@gmail.com
Hi I'm writing a plugin and want it to depend on another plugin installed. At the moment I just have a line source in my plugin that pulls in that plugin. Is there a standard way of doing this or do plugin authors just invent their own way? Could I use Vundle here instead? -- -- You