-
Notifications
You must be signed in to change notification settings - Fork 255
v2.x; Neo-tree shows nothing. #184
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
Comments
We don't actually have any commands that start with Does it work if you run these?
|
Those are defined in Sorry for the confusion: custom commands I had are like:
Of course I did try all of them including the new command: Actually even with the zero config (i.e., no |
I tried setting log level to TRACE but I don't see any debugging message. 8 Tests are just failing -- all saying like nothing is printed on the sidebar.
I actually found something: this has something to do with neovim itself. I was neovim nightly (NVIM v0.7.0-dev+1283-g77eb6f9dc in my case) where neotree is broken. However, with neovim 0.6.1 stable, the v2 branch works! Could you please try the plugin with nightly neovim? |
I guess you are compiling from source because that commit is 3 hours old! It works on nightly, but that last commit looks like something that may break things. I'll compile and take a look. |
I checked out the same commit and compiled and I don't have the same problem, although my syntax highlighting is completely broken. Perhaps there is something in your config that is broken in a way that affects neo-tree? With the logging, you do need to set |
I had this happen too. I see that your files are in a directory named ".dotfiles". If you press 'H' (as in shift + h) the files should be shown. You can also set the filesystem filters to always show hidden files. I don't know if this is the intended behaviour though. |
That has to be it! With 1.x, the fact that a directory should be hidden was ignored when that directory was a root directory. You could actually call that a bug, but it was also a more intuitive outcome. I'll reinstate that behavior now. |
The latest commit in main / v2.x fixes the issue of hiding the root folder. Please let me know if that was the cause of your issue @wookayin. |
In my example above, the root directory was a working copy of the neo-tree.nvim repository: On Indeed any subdirectory under I feel like the root directory is visible because of the specific condition introduced in cab3a2e but it is not effective for any of the subtree. I don't think the fix was enough. |
OK, now I think it's right. Thanks for your help figuring it out. |
@cseickel Thank you very much for the prompt fix! The 2.0-rc3 version works well! |
BTW, don't you need to remove legacy NeoTreeSomething commands (by default unless an user explicitly bring them back?) |
I would love too, but that constitutes a breaking change, and my promise is that there are no breaking changes without a deprecation period. 2.x is the deprecation period for those commands, and they will be completely removed in 3.x. |
Yes thanks! I respect those decisions. You may also want to print deprecation warnings when those command are ran, but anyway we have this documented and announced so it should be fine.. |
Probably related to this, at the current sometimes it correctly show the folder structure, sometimes it shows an error:
Update: I just switch to the bug1.mov |
4831beb (HEAD -> v2.x, origin/v2.x)
My neotree config
Note: this was working OK in v1.x, the only change is
hijack_netrw_behavior
renaming:What happens: it literally shows nothing, on every
:NeoTree
-opening commands.The text was updated successfully, but these errors were encountered: