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 read the appropriate plugin's documentation.
I have searched that this issue has not been reported before.
By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.
Describe the bug
When installing Neo-Tree via the line in the kickstart file
require 'kickstart.plugins.neo-tree',
somehow no help file for the plugin is available.
Whereas installing the plugin via the minimal kickstart of their README, we correctly have the help files available in neovim
To Reproduce
Install kickstart
Uncomment line quoted above
restart neovim, lazy will install neo-tree correctly
run :h neo-tree
See that it is not available
Desktop
OS: MacOS
Terminal: iterm2
Neovim Version
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1727870382
Run ":verbose version" for more info
The text was updated successfully, but these errors were encountered:
Hey @adamency,
In kickstart's config neotree is lazy loaded i.e it isn't loaded until you run :Neotree. That is why :h neo-tree command is not available. If you want you can change the config to load it on startup.
Before Reporting an Issue
I have read the kickstart.nvim README.md.
I have read the appropriate plugin's documentation.
I have searched that this issue has not been reported before.
By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.
Describe the bug
When installing Neo-Tree via the line in the kickstart file
somehow no help file for the plugin is available.
Whereas installing the plugin via the minimal kickstart of their README, we correctly have the help files available in neovim
To Reproduce
:h neo-tree
See that it is not available
Desktop
Neovim Version
The text was updated successfully, but these errors were encountered: