-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session.vim with NERDTree: One tab disappears on OpenSession #28
Comments
Not completely sure if it's the same issue but I'm also running into issues while opening a saved session w/ NERDTree open in every tab. In my setup, I have NERDTree open in the left split in EVERY tab (TextMate-style Rails development). When I reopen the session (which had 2 tabs open with a file + NERDTree in each tab), the first tab looks OK but the second tab opens with 4 splits - one with NERDTree, one contains an empty file (titled "No Name") and the last two splits contain the file that should've been opened instead of "No Name" in the second split alone. |
The issue reported by @eric-hu should be fixed in version 2.4.1 (just released). |
@baseliners After fixing the issue reported by @eric-hu I can not reproduce the issue you reported. Can you try version 2.4.1 to see whether it resolves the problem for you? |
Thanks for the update @xolox ! Confirmed that this fixes my original issue (after adding "Bundle 'xolox/vim-misc'" to my .vimrc to setup Vundler). |
Just a note to anyone else running into this - if you open gvim from the terminal and specify the session file using -S, the session is restored correctly without the additional splits. i.e. gvim -S <path_to_session_file.vim> |
I normally browse with NERDTree open in the current project folder. NERDTree sits in its own tab (at tab position 0) and I open each project file in a new tab.
Using either
:SaveSession
or autosave, I can reload my last session, but one tab is missing--the one next to the NERDTree tab.If I keep a file open in the same tab as NERDTree, this doesn't seem to happen.
The text was updated successfully, but these errors were encountered: