Robert Webb wrote:
> > > I use vim sessions a lot. I use the .vse extension and have them
> > > associated with 'gvim.exe -c "source %1"' so I can double click on
> > > them. It's nice when they start up without requiring an enter to
> > > continue. However there were two I started up today that both
> > > required me to hit enter. Here's what they said:
> > >
> > > (1) "Snd.txt" 851L, 25834C
> > > 1 buffer wiped out
> > >
> > > (2) "4D.cpp" 8929 lines --85%-- ((1) of 3)
> > > "Model3D.cpp" 11705 lines, 300296 characters
> > > Press ENTER or type command to continue
> > >
> > > What does "buffer wiped out" mean? All the windows appeared to
> > > load correctly once I hit enter. I seem to get this a lot.
> > >
> > > The second case had multiple tabs. Multiple windows in one tab
> > > don't require a hit-enter, so hopefully this can be avoided
> > > somehow for multiple tabs too.
> >
> > This is because some options, especially 'shortmess' are restored
> > after the first tabpage instead of after the last one. I'll move
> > the commands, that should fix this.
>
> I just tried 7.0g03. Now it doesn't scroll due to file-loading
> messages with multiple tabs, but it still always scrolls with or
> without tabs due to the "1 buffer wiped out" message.
Is that with a newly created session file? Strange. It should contain
something like this:
if expand('%') == '' && !&modified && line('$') <= 1 && getline(1) == ''
let s:wipebuf = bufnr('%')
endif
set shortmess=aoO
Thus 'shortmess' is restored only after wiping out the buffer.
--
How To Keep A Healthy Level Of Insanity:
9. As often as possible, skip rather than walk.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
