On Wed, Dec 17, 2008 at 5:44 AM, Nicolas Aggelidis
<[email protected]> wrote:
>
> hi to all the list,
>
> i have the following problem , and once again i need your help.
>
> i have the following configuration for sessions:
>
> set sessionoptions+=resize
> set sessionoptions+=slash
> set sessionoptions+=unix
> set sessionoptions+=winpos
>
> to save a session i do: mksession ~/sessions/session_name.vim
> and to load a session i do: source ~/sessions/session_name.vim
>
> The problem is observable with files on different folders, for example if i
> have
>
> ~/folder/file1
> ~/folder/file2
> ~/folder/folder2/file3
>
> I open them {in this orded if it matters} on different tabs and then i issue a
> mksession ~/sessions/sample.vim
>
> then on a different gvim i do
>
> source ~/sessions/sample.vim
>
> the result is that gvim opens all files on different tabs, *but* the
> file3 is blank! {file3 is the file on the different directory than the
> other 2.
>
>
> the sessions work great if i load gvim with -u NONE and then save the
> session option...
> and then open them from a gvim -u NONE.
>
> sessions fail if i save from a gvim -u NONE but try to open them from
> a "normal" gvim..
>
>
> any idea why this happens? maybe some other setting is causing it?{but which?
Likely, you have 'autochdir' set somewhere in your startup files. You
can find out which file by executing ":verbose set autochdir". That
setting used to cause problems for me when reloading sessions. I used
to work around this problem with an autocommand similar to this:
autocmd BufWinEnter * exe 'lcd ' . expand('%:h')
I eventually quit using this for reasons I can't recall. It may have
problems as well.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
