-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Error detected while processing BufLeave Auto commands for "NERD_tree_*" #745
Comments
@Git-leng, you didn't include any information about the version of Vim you are using, or about the version of the NERDTree you are using (i.e., please include a commit hash). You must include all relevant information for anyone to make an assessment of your problem. |
Closing due to inactivity. |
I am having the same problem with Vim 8.0.707 (installed via Debian package manager). This only happens when I restore from a saved session with a NERDTree window in it. OS Info
Vim Info
To reproduce:
Upon restoring the session:
|
NERDTree windows cannot be restored with vim sessions. If you look at the session file, you'll see that vim is splitting the window, and renaming a new buffer to "NERD_tree_1", but it's still empty. NERDTree doesn't save the tree to disk, so it cannot be restored. Only a call to |
I just run into a similar issue (with `thaerkh/vim-workspace).
I don't care whether the NERDTree buffer is restored, but I'd rather get rid of the error above that I get when NERDTree was opened while exiting vim. Is there a workaround? |
I get this error many times every day when I get to work and I load my session. |
It looks like tweaking the set sessionoptions-=blank Your session file will not restore and empty windows you had, but in most cases, that's probably an acceptable trade-off. |
Thank you! Indeed it fixed the stream of error messages I was getting, but now sometimes it modifies my layout when I had other "special" (plugin) windows that appear empty on session load |
Error info!
The text was updated successfully, but these errors were encountered: