-
-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Highlight definitions taking ~6seconds (JavaScript and TypeScript) #435
Labels
bug
Something isn't working
Comments
Hi ! Can you paste the output of |
Ah, that could be it? it's: |
indeed it looks like it is! 🎉 Thanks Thomas for the quick help!! 👏 |
Thanks for reaching out ! |
stsewd
added a commit
to stsewd/nvim-treesitter
that referenced
this issue
Sep 11, 2020
vigoux
pushed a commit
that referenced
this issue
Sep 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hello,
When I move my cursor over a variable, it takes about 6 seconds for the highlighting to show (highlight) the other references of that variable.
On the other hand,
highlight_current_scope
is instantaneous.To Reproduce
Steps to reproduce the behavior:
I have a pretty minimal
init.vim
right now, I removed coc.vim, no lsp plugin and even did:syntax off
.I only have the JavaScript and TypeScript languages installed for treesitter.
Expected behavior
I would expect the highlighting of other references under the cursor to be instantaneous.
Output of
:checkhealth nvim_treesitter
health#nvim_treesitter#check
Installation
git
executable found.cc
executable found.typescript parser healthcheck
highlights.scm
found.locals.scm
found.textobjects.scm
found.fold.scm
found.javascript parser healthcheck
highlights.scm
found.locals.scm
found.textobjects.scm
found.fold.scm
found.Output of
nvim --version
Additional context
Everything else seems to work correctly! ❤️ 👍
Maybe related to #151 ? (It does not block cursor movement for me though)
Update
My
init.vim
config for treesitter:The text was updated successfully, but these errors were encountered: