nvim-treesitter / nvim-treesitter/nvim-treesitter-context
Allow jumping to nearest context with go_to_context()
Nobody has claimed this yet.
- Dominant language
- Janet
- Stars
- 3.2k
- Forks
- 241
- PR merge metrics
- No merged PRs in 30d
Description
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 are also displayed by the plugin, and I'd like this mapping to be more granular and also consider contexts that are in view, or hidden by my max_lines setting.
I managed to hack something together if I expose the iter_context_parents function from the plugin:
-- add in `lua/treesitter-context/context.lua`
M.iter_context_parents = iter_context_parents
-- in my mapping:
local context = require('treesitter-context.context')
local cursor = vim.api.nvim_win_get_cursor(0)
local row = cursor[1]
local parents, _query = context.iter_context_parents(0, { row - 1, 0, row - 1, 0 })()
for i = 1, #parents do
local parent_row = parents[i]:range() + 1
if parent_row < row then
vim.cmd([[ normal! m' ]])
vim.api.nvim_win_set_cursor(0, { parent_row, 0 })
vim.cmd.normal('^')
return
end
end
This seems to work how I want, and now I wonder what it would take to implement a cleaner version of this inside the plugin, or what bits could be exposed to allow a custom mapping like this (iter_context_parents seems a bit too low-level).
Also not sure if there's a way to do this using e.g. nvim-treesitter-textobjects, it seems the magic sauce that's needed are the queries collected in this plugin.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in lua/treesitter-context/context.lua by reading go_to_context() and the iter_context_parents() entry point shown in the issue. Compare the requested behavior with the current max_lines filtering and determine a cleaner exposed API. Done means a mapping can jump to the nearest parent context in view, including contexts hidden by max_lines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, neovim
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100