fix: fallback to filetype for get_lang for treesitter highlight preview#2867
Merged
Conni2461 merged 1 commit intoJan 18, 2024
Merged
Conversation
Member
|
thanks :) |
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
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.
Description
nvim-treesitteris in the middle of a rewrite, and will switch to the rewrite once Neovim 0.10 is released. In this rewrite, there is something that has changed with registering a language. This introduces an issue in telescope, where it is not always able to provide treesitter highlighting in the preview.Reading the code in
nvim-treesitter, it also usesvim.treesitter.language.get_langand always fallback to the filetype if the function doesn't provide any languageType of change
Please delete options that are not relevant.
How Has This Been Tested?
Install the newest
nvim-treesitterusing themainbranch. Try to open a picker with a previewer, and notice that some languages where the filetype name matches the parser name, and see that it is not properly highlighted.Configuration:
Checklist: