Re: [patch] runtime path doc patch

2018-04-19 Fir de Conversatie Bram Moolenaar
Christian wrote: > > Bram, > > can you please include the following change in the next runtime update? > > Here is another small doc patch. This might explain the following behaviour: > > ./vim --clean '-c :e foobar' -c ':au WinEnter echom "Entering Window > for buffer ". expand("")' > > The

Re: [patch] runtime path doc patch

2018-04-19 Fir de Conversatie Christian Brabandt
On Mi, 18 Apr 2018, Christian Brabandt wrote: > Bram, > can you please include the following change in the next runtime update? Here is another small doc patch. This might explain the following behaviour: ./vim --clean '-c :e foobar' -c ':au WinEnter echom "Entering Window for buffer ". expan

Re: [patch] runtime path doc patch

2018-04-18 Fir de Conversatie Christian Brabandt
On Mi, 18 Apr 2018, Bram Moolenaar wrote: > > Christian wrote: > > > can you please include the following change in the next runtime update? > > > > I have had now already twice the case¹ that a user of vim-airline has > > been using the plugin directory for cloning packages. That made the >

Re: [patch] runtime path doc patch

2018-04-18 Fir de Conversatie Bram Moolenaar
Christian wrote: > can you please include the following change in the next runtime update? > > I have had now already twice the case¹ that a user of vim-airline has > been using the plugin directory for cloning packages. That made the > plugin break miserably. So put a note into the standard d

[patch] runtime path doc patch

2018-04-18 Fir de Conversatie Christian Brabandt
Bram, can you please include the following change in the next runtime update? I have had now already twice the case¹ that a user of vim-airline has been using the plugin directory for cloning packages. That made the plugin break miserably. So put a note into the standard documentation that this