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
Hey, 👋
Just stumbled over this plugin and it looks pretty cool/powerful.
I must admit that I dislike to set key mappings via a setup function of a plugin. Happily other treesitter plugins have added a Vim command. Or at least there is a "direct" Lua function available that could be bound. But for this plugin I don't understand the internals and how to do a manual mapping.
Could you help me? Or eventually add commands for these possible mappings? 🙃
The text was updated successfully, but these errors were encountered:
you can call the lua methods that produce the results from the prebuilt mappings. The most common one is require "nvim-tree-docs.internal".doc_node_at_cursor(). I will look at exposing commands.
Note, this plugin is in some flex due to the rapid development of treesitter in neovim. I'm using it daily, but there MAY be times when it may be broken.
Hey, 👋
Just stumbled over this plugin and it looks pretty cool/powerful.
I must admit that I dislike to set key mappings via a setup function of a plugin. Happily other treesitter plugins have added a Vim command. Or at least there is a "direct" Lua function available that could be bound. But for this plugin I don't understand the internals and how to do a manual mapping.
Could you help me? Or eventually add commands for these possible mappings? 🙃
The text was updated successfully, but these errors were encountered: