nvim-treesitter-context icon indicating copy to clipboard operation
nvim-treesitter-context copied to clipboard

Show code context

Results 61 nvim-treesitter-context issues
Sort by recently updated
recently updated
newest added

Hi, first of all, thanks a lot for this awesome plugin! I'm heavily using/relying on the relative numbers of the context and sometimes I'd find it really helpfull if I...

enhancement

I wanted to have a mapping to jump to whatever is the current "parent" node, and found the `go_to_context()` function which works great! But it only jumps to contexts that...

enhancement

### Description Recently, the markdown queries bundled with nvim-treesitter were updated to capture the entire line of headers rather than the individual prefix and title text components (https://github.com/nvim-treesitter/nvim-treesitter/pull/6766). These new...

bug
query issue

### Description I noticed some things such as treesitter syntax highlighting and .editorconfig weren't applying at startup (when passing files as arguments to nvim). I tracked the culprit down to...

bug

It's a bit rough, but I tried to resolve #442. Apparently, there are cases where line -1 is specified. So, in that case, I tried not to process it.

# Description This PR fixes an issue where sometime the `ctx_lines` used to define the `height` were empty, triggering an error about invalid height: ``` lua/treesitter-context/render.lua:51: 'height' key must be...

### Description With `vim.opt.number = true`, while editing a markdown file where the first line is empty, the plugin will crash when you have scrolled far down enough for the...

bug

### Description When I open the command line window with q: I get the following error message: ``` Error executing vim.schedule lua callback: ...vim-treesitter-context/lua/treesitter-context/render.lua:310: E11: Invalid in command-line window; executes,...

bug
unable to reproduce

### Description No root-level header causes incorrect API calls. ### Neovim version 0.9.5 ### Expected behavior No error. If there is no available context, do not try to display anything....

bug