>
> That is a reasonable request. If the "start" packages were not loaded
> then :packadd can also look there.
>
When I saw these replies I thought, "well now I have some vacation days, this
is a good time to try to go and implement this".
But I see Bram already added it himself, so Thank
Alejandro Hernandez wrote:
> Testing plugins in isolation is frequently done. Under the current
> system, all
> plugins one wants to test have to be moved under `opt` to be able to
> use `:packadd`. Relying on `:runtime` is both error-prone and
> cumbersome. There's no need for the user to
Testing plugins in isolation is frequently done. Under the current system, all
plugins one wants to test have to be moved under `opt` to be able to use
`:packadd`. Relying on `:runtime` is both error-prone and cumbersome. There's no
need for the user to replicate `:packadd` functionality using
skeept wrote:
> On Monday, August 14, 2017 at 11:16:50 PM UTC-5, Tony Mechelynck wrote:
> > On Tue, Aug 15, 2017 at 5:44 AM, skeept wrote:
> > > I have some plugins in the locations:
> > >
> > >
> > > ~/.vim/pack/bundle/start
> > > ~/.vim/pack/bundle/opt
> > >
> > > if I start vim with
> > > vim
On Tue, Aug 15, 2017 at 6:14 PM, skeept wrote:
> On Monday, August 14, 2017 at 11:16:50 PM UTC-5, Tony Mechelynck wrote:
>> On Tue, Aug 15, 2017 at 5:44 AM, skeept wrote:
>> > I have some plugins in the locations:
>> >
>> >
>> > ~/.vim/pack/bundle/start
>> >
On Monday, August 14, 2017 at 11:16:50 PM UTC-5, Tony Mechelynck wrote:
> On Tue, Aug 15, 2017 at 5:44 AM, skeept wrote:
> > I have some plugins in the locations:
> >
> >
> > ~/.vim/pack/bundle/start
> > ~/.vim/pack/bundle/opt
> >
> > if I start vim with
> > vim --noplugins
> > vim -u NONE
> >
> >
On Tue, Aug 15, 2017 at 5:44 AM, skeept wrote:
> I have some plugins in the locations:
>
>
> ~/.vim/pack/bundle/start
> ~/.vim/pack/bundle/opt
>
> if I start vim with
> vim --noplugins
> vim -u NONE
>
> then I can load plugins from opt but not from start.
> So if a plugin say,