Native treesitter preview fallback#180
Open
madlep wants to merge 3 commits into
Open
Conversation
nenahp
reviewed
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using native neovim treesitter, and https://github.com/romus204/tree-sitter-manager.nvim (or something else similar, or manual file handling) to manage treesitter parsers after "the drama", bqf previews don't have treesitter syntax highlighting.
Fix this by tolerating
nvim-treesitter.parsersnot being present, and let the existing logic do it's thing.It looks like this is the way that code was supposed to work, but because
initializedis alwaysfalse, it was never setting up the fallback logic to use native treesitter functions.