Skip to content
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

NERDTree.TreeNotOpen thrown when opening Neovim into NERDTree #1408

Closed
sjshuck opened this issue Feb 11, 2024 · 4 comments · Fixed by #1409
Closed

NERDTree.TreeNotOpen thrown when opening Neovim into NERDTree #1408

sjshuck opened this issue Feb 11, 2024 · 4 comments · Fixed by #1409
Labels

Comments

@sjshuck
Copy link

sjshuck commented Feb 11, 2024

First reported as a comment to #1347 and moved here per @rzvxa.

I don't know when it started happening (it was a few weeks ago I feel), or whether it's the same issue, but I am getting a similar error. When I launch directly into NERDTree with nvim . and then open a file with s, it produces this error:

Error detected while processing function nerdtree#ui_glue#invokeKeyMap[1]..76[18]..75[3]..<SNR>29_openVSplit[1]..105[1]..121[3]..177[6]..178[9]..172[3]..176[16]..218[1]..228[2]..function nerdtre
e#ui_glue#invokeKeyMap[1]..76[18]..75[3]..<SNR>29_openVSplit[1]..105[1]..121[3]..177[6]..178[9]..172[3]..176[16]..218[1]..228:
line    2:
E605: Exception not caught: NERDTree.TreeNotOpen

Note that this only errors with s, not with i, and only when launching directly into nvim ., not when explicitly firing up NERDTree after Neovim via nvim -c ':NERDTree'.

I have also observed this on a Mac

@rzvxa
Copy link
Member

rzvxa commented Feb 11, 2024

I found the issue and created a merge request for it, Give it a spin and let me know if that resolves your issue completely or if it still persists.

@sjshuck
Copy link
Author

sjshuck commented Feb 11, 2024

That fixes it for me!

@rzvxa
Copy link
Member

rzvxa commented Feb 11, 2024

That's great! I've merged the PR and now you can update to the latest commit on the master branch.
Thanks again for reporting the issue, And I'm sorry for this inconvenience.

@sjshuck
Copy link
Author

sjshuck commented Feb 11, 2024

sorry for this inconvenience

Are you kidding? This is the most convenience I've ever experienced in the open source world.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants