Percy Foreman wrote:
> "Charles Campbell" <[EMAIL PROTECTED]>:
>
>   
>> fritzophrenic wrote:
>>     
>>> On Nov 4, 6:55 am, "Percy Foreman" <[EMAIL PROTECTED]> wrote:
>>>
>>>       
>>>> Hi all,
>>>>
>>>> I've been trying to incorporate tabs in my workflow, but have trouble
>>>> saving them in a session. I usually start with an existing session,
>>>> make new tabs and source different sessions into each of the tabs.
>>>> Then I save a new session-file, hoping it will remember all my tabs.
>>>>
>>>> But it doesn't. When I exit vim and fire up the newly created session,
>>>> I find that all the files are there, but all the tabs are gone.
>>>> Searched google, but "tabs" seems to be too popular to get a correct
>>>> answer.
>>>>
>>>> Thanks,
>>>> Percy
>>>>
>>>>         
>>> I personally have found the support for tabs in sessions for the
>>> Windows version of Vim to be so abysmal that I do not use sessions at
>>> all.
>>>
>>> This is okay for me, because I often end my Vim sessions with many
>>> buffers loaded that I will probably not need the next time I start up
>>> Vim. For my purposes, the excellent MRU plugin is all I need (though I
>>> really need to increase the number of files remembered again...)
>>>
>>>       
>> I don't often make tabs and sessions -- but I just tried making a
>> session with three tabs, one of which was a split window.  Did the
>> :mksession somefile.ses, exited, and  gvim -S somefile.ses, and it was
>> restored correctly.  Does your sessionoptions setting have "tabpages" in it?
>>
>> Regards,
>> Chip Campbell
>>
>>     
>
> I did not have a "sessionoptions"-setting in my .vimrc. I just changed it to
>
> set ssop="blank, buffers, curdir, folds, help, options, winsize, tabpages"
>
> but get the same result.
>   
As Fritzophrenic pointed out, plugins apparently have the potential to 
interfere.  Try:

vim -u NONE
  (:set nocp, set up tabs and whatnot)
  :mks! ses.S
  :q

If that works  (vim -S ses.S), try

vim --noplugin
  (same as above)

If the first case worked, then there's likely to be a conflict with 
something in your .vimrc or plugins.  If the second case works, that'll 
narrow it down to your plugins.  Further narrowing is an exercise in 
disabling plugins and re-enabling them.

Regards,
Chip Campbell


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to