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
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
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
>
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
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