Re: Extraneous BufUnload event triggered

2013-07-22 Fir de Conversatie Bram Moolenaar
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

Re: Extraneous BufUnload event triggered

2013-07-22 Fir de Conversatie Marcin Szamotulski
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

Extraneous BufUnload event triggered

2013-07-22 Fir de Conversatie Pokey Rule
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