> Wel already do use :argadd actually, when starting with "vim file1
> file2". The first buffer is wiped out, we just don't have buffer number
> one.
I think this is not true if 'hidden' is set. I failed to include that in
my example
though. Sorry for being unclear there. With 'hidden' the bu
Jason Franklin wrote:
> > Perhaps using :argadd works to create the buffers without actually
> > opening them or any other side effects. Then later reset the
> > argument list.
>
> I think it's even trickier than using :argadd. For example...
>
> vim --clean
> :argadd test.txt
> :e tes
Bram,
> Perhaps using :argadd works to create the buffers without actually
> opening them or any other side effects. Then later reset the
> argument list.
I think it's even trickier than using :argadd. For example...
vim --clean
:argadd test.txt
:e test.txt
Notice that you're now editin
Christian wrote:
> On Di, 21 Mai 2019, Jason Franklin wrote:
>
> > > Does this also fix https://github.com/vim/vim/issues/4352 I suppose not?
> >
> > No, it does not fix that issue.
> >
> > However, I'm not exactly sure that the issue referenced is a valid
> > complaint. It was my understand
On Tue, May 21, 2019 at 2:31 PM Jason Franklin
wrote:
>
> > Does this also fix https://github.com/vim/vim/issues/4352 I suppose not?
>
> No, it does not fix that issue.
>
> However, I'm not exactly sure that the issue referenced is a valid
> complaint. It was my understanding that buffer numbers
On Di, 21 Mai 2019, Jason Franklin wrote:
> > Does this also fix https://github.com/vim/vim/issues/4352 I suppose not?
>
> No, it does not fix that issue.
>
> However, I'm not exactly sure that the issue referenced is a valid
> complaint. It was my understanding that buffer numbers are simply
> Does this also fix https://github.com/vim/vim/issues/4352 I suppose not?
No, it does not fix that issue.
However, I'm not exactly sure that the issue referenced is a valid
complaint. It was my understanding that buffer numbers are simply id
numbers and shouldn't be relied upon for anything oth
On Mo, 20 Mai 2019, Jason Franklin wrote:
> When restoring a session that has multiple tab pages, the current
> window for each tab page is not restored as expected. The new test
> below currently fails but should pass:
Does this also fix https://github.com/vim/vim/issues/4352 I suppose not?
When restoring a session that has multiple tab pages, the current
window for each tab page is not restored as expected. The new test
below currently fails but should pass:
diff --git a/src/testdir/test_mksession.vim b/src/testdir/test_mksession.vim
index bc41396..80bedfc 100644
--- a/src/testdir
