search

nvim-treesitter / nvim-tree-docs

Code documentation built with treesitter
225 stars 10 forks source link

Insufficient documentation regarding keymaps #8

Open goncalves-diogo opened 3 years ago

goncalves-diogo commented 3 years ago

Hi, I'm currently trying to get this to work on my workflow and i can't reach any breakthrough.

My current configuration file has:

tree_docs = {
    enable = true,
    keymaps = {
        doc_node_at_cursor = "<leader>a"
        },
  },

I was trying to remap doc_node_at_cursor to a. However i can't seem to get this to work. I've also ran :nmap in order to see all the normal mappings and it is not mapped at all

Mte90 commented 3 years ago

I agree with that I see that also the default hotkey is not mapped in vim.

steelsojka commented 3 years ago

Since this is an nvim-treesitter module you can find the documentation for it in that repo. As far as them not working, that would be bug. We'll need to figure out why they arent working.

On Sun, Jul 11, 2021, 6:50 AM Daniele Scasciafratte < @.***> wrote:

I agree with that I see that also the default hotkey is not mapped in vim.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvim-treesitter/nvim-tree-docs/issues/8#issuecomment-877785846, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPXOSWCCRGCLMI4HKDOU2LTXGAOTANCNFSM474VF7CQ .

nathanielks commented 2 years ago

Noting for future readers: I haven't been able to figure out why, but I think this plugin can't map when something else exists at the beginning of the map. That's a poor way of explaining, so hopefully this is clearer: the default mapping is gdd. If you have any mapping that begins with g, the mapping won't apply. I think this is also why mapping to <leader> doesn't work, either. The way I figured it out was by trying different mappings and found one that didn't have anything (for me, this was fb).