You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the web for an answer to my question.
Environment (for bug reports)
Operating System: MacOS 10.15.4
Vim/Neovim version :echo v:version: vim 801
NERDTree version, found on 1st line in NERDTree quickhelp ?: 6.7.0
vimrc settings
NERDTree variables
let NERDTreeShowHidden=1let NERDTreeIgnore=['\.DS_Store$', '\.swp$', '\.git$']
let NERDTreeShowLineNumbers=1let NERDTreeMinimalUI=1let NERDTreeWinSize=35letg:NERDTreeStatusline='NERDTree'
Other NERDTree-dependent Plugins
jistr/vim-nerdtree-tabs
ryanoasis/vim-devicons
tiagofumo/vim-nerdtree-syntax-highlight
Xuyuanp/nerdtree-git-plugin
Others (specify):
I've verified the issue occurs with only NERDTree installed.
Steps to Reproduce the Issue
Create two files in an empty directory: file1.txt and file2.txt.
Open vim in that directory.
Open file1.txt with nerdtree o.
Open file2.txt with nerdtree o.
Delete buffer where file1.txt is open :bd {buffer number}
Open file1.txt as vsplit with nerdtree s
Current Result (Include screenshots where appropriate.)
You get a new empty buffer on the buffer list, in this case it was the buffer 4 [No Name]:
If you do the 6 steps and keep quitting :q the file1.txt and opening again with vsplits, it keeps creating new empty buffers. Note that this time I didn't delete the buffer, I just quit the file with :q. This means that you only have to delete the buffer once and keep using vsplits for it to trigger the issue multiple times. This is after quitting and opening the same file 3 times:
Expected Result
The expected result should be the two files open on vsplit without having to create a new empty buffer. Since it has another open file on vim, it shouldn't have to open a new empty buffer. This expected behavior is what happens when you use split command on nerdtreei instead of vsplits. They should behave the same when it comes to handling the buffers:
Comments
I already have the solution to this problem on my forked repository. I created this issue because this seems like a bug but I don't know if this is actually the correct behavior.
The text was updated successfully, but these errors were encountered:
Self-Diagnosis
:h NERDTree
Environment (for bug reports)
:echo v:version
: vim 801?
: 6.7.0Steps to Reproduce the Issue
file1.txt
andfile2.txt
.o
.o
.:bd {buffer number}
s
Current Result (Include screenshots where appropriate.)
You get a new empty buffer on the buffer list, in this case it was the buffer
4 [No Name]
:If you do the 6 steps and keep quitting
:q
the file1.txt and opening again with vsplits
, it keeps creating new empty buffers. Note that this time I didn't delete the buffer, I just quit the file with:q
. This means that you only have to delete the buffer once and keep using vsplits
for it to trigger the issue multiple times. This is after quitting and opening the same file 3 times:Expected Result
The expected result should be the two files open on vsplit without having to create a new empty buffer. Since it has another open file on vim, it shouldn't have to open a new empty buffer. This expected behavior is what happens when you use split command on nerdtree
i
instead of vsplits
. They should behave the same when it comes to handling the buffers:Comments
I already have the solution to this problem on my forked repository. I created this issue because this seems like a bug but I don't know if this is actually the correct behavior.
The text was updated successfully, but these errors were encountered: