perf: improve general treesitter performance and markdown particular performance #423
Conversation
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
TheLeoP
changed the title
Contributor
Author
|
I added a second commit removing one of the queries added to |
Contributor
Author
|
#416 (comment) explains why that particular Latex pattern was freezing Neovim |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Partially fixes #416
I've been having some performance issues just after opening markdown buffers since support for it was added. This PR improves the performance for treesitter (specially for the
markdownbuffer opened byvim.lsp.buf.hover).I'm still having performance issues from time to time, but I haven't been able to track it down further. Something in the
get_memoized_matchesfunctions is (sometimes) taking a second and a half (on my particular hardware) on a new, empty, markdown buffer when typing`as the first character in the buffer. But, for now, I've disabled vim-matchup in insert mode as a workaround instead (vim.g.matchup_matchparen_nomode = "i").I'll open another PR in the future if I found the source of my other performance issue.