Consider the following code:
% vim -u NONE -i NONE --cmd 'autocmd BufReadCmd edit://foo :call
setline(".", "foo")|setlocal buftype=nofile' -c 'edit edit://foo' -c 'mksession
ses.vim' -c qall!
% vim -u NONE -i NONE --cmd 'autocmd BufReadCmd edit://foo :call
setline(".", "foo")|setlocal buftype=nofile' -S ses.vim
. This will show you the empty buffer in the second Vim instance with an empty
name. But the following code:
% vim -u NONE -i NONE --cmd 'autocmd BufReadCmd edit://foo :call
setline(".", "foo")|setlocal buftype=nofile' -c 'edit edit://foo' -c 'edit bar'
-c 'mksession ses.vim' -c qall!
% vim -u NONE -i NONE --cmd 'autocmd BufReadCmd edit://foo :call
setline(".", "foo")|setlocal buftype=nofile' -S ses.vim -c bnext
(additions: `-c 'edit bar'` in first command, `-c bnext` in the second) will
show you buffer with `foo` on the first line.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
