> Version 7.3 with gVim (Windows) and MacVim, with set
> sessionoptions="buffers,sesdir,folds,tabpages" the tabs are not
> restored.
>
> The Windows version is a default install and the Mac one is started
> with -u NONE -U NONE, then upon opening I set ssop. I open
> file[1-5].txt from a temp folder and create tabs as following: Tab 1
> has vsplit(file1, file2), Tab 2 has split file3 with vsplit(file4,
> file5). After the setup I call :mksession.
> After restarting Vim with the same options, I set ssop, then
> call :source Session.vim and observe that only the last active tab is
> restored, but all the files are loaded in buffers.
'ssop' needs to be set properly just before creating the session file.
It doesn't matter what 'ssop' is set to when sourcing the session file.
The session file is just a script, and Vim executes its contents
unconditionally. I haven't yet seen any 'ssop' checks in a session file
script (wouldn't make sense either (you could only *disable* session
features)).
In your session file, there should be commands like :tabnext or :tabedit
... but they are not there.
Looks like "tabpages" was not included in 'ssop' when the session file
was created (strange though, as "tabpages" is part of the 'ssop' default
value).
> The two Session.vim files, one for Windows one for Mac, are here:
> https://gist.github.com/1437522/. I compared them and the only
> difference is pretty much the paths.
>
> I expected that "tabpages" would be enough to restore the tabs: "all
> tab pages; without this only the current tab page is restored, so that
> you can make a session for each tab page separately". With the default
> options, the tabs are loaded properly (but I don't want to persist the
> mappings, etc).
>
> What am I doing wrong?
--
Andy
--
You received this message from the "vim_use" 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
No comments:
Post a Comment