nvim-treesitter / nvim-treesitter/nvim-treesitter-context

No handler for match-percent-separator for nvim 0.12.1

Open
#670 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Janet
Stars
3.2k
Forks
241
PR merge metrics
No merged PRs in 30d

Description

after upgrade nvim- 0.12.1
sometime cause bug

vim.schedule callback: ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:215: ...m/0.12.1/share/nvim/runtime/lua/vim/treesitter/query.lua:839: No handler for match-percent-separator?
stack traceback:
	[C]: in function 'f'
	...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:215: in function 'tcall'
	...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:596: in function 'parse'
	...im-treesitter-context/lua/treesitter-context/context.lua:239: in function 'get_parent_langtrees'
	...im-treesitter-context/lua/treesitter-context/context.lua:267: in function 'iter_context_parents'
	...im-treesitter-context/lua/treesitter-context/context.lua:364: in function 'get'
	...ugins/nvim-treesitter-context/lua/treesitter-context.lua:113: in function 'f'
	...ugins/nvim-treesitter-context/lua/treesitter-context.lua:60: in function <...ugins/nvim-treesitter-context/lua/treesitter-context.lua:40>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported failure on Neovim 0.12.1, then start in lua/treesitter-context/context.lua around get_parent_langtrees and compare it with the Neovim stack locations shown in the report. Trace the match-percent-separator error during parsing; done means the context plugin no longer triggers this error in the affected scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.