Pokey Rule wrote:
> I run vim with no file on the command-line, so that it shows the
> scratch buffer. When I then run
>
> :e foo
>
> to edit file 'foo', there is a BufUnload event triggered for file
> 'foo'. Here is a test vim command that I use to demonstrate the issue:
>
> autocmd BufUnload
On 17:51 Mon 22 Jul , Bram Moolenaar wrote:
>
> Pokey Rule wrote:
>
> > I run vim with no file on the command-line, so that it shows the
> > scratch buffer. When I then run
> >
> > :e foo
> >
> > to edit file 'foo', there is a BufUnload event triggered for file
> > 'foo'. Here is a test vim
I run vim with no file on the command-line, so that it shows the scratch
buffer. When I then run
:e foo
to edit file 'foo', there is a BufUnload event triggered for file 'foo'. Here
is a test vim command that I use to demonstrate the issue:
autocmd BufUnload * echom "Unloaded " . expand("")
I