Open EricDriussi opened 2 years ago
Switching from <buffer>
to *
in the problematic lines seem to work just fine :thinking:
So from
autocmd CursorHold <buffer> lua vim.lsp.buf.document_highlight()
autocmd CursorMoved <buffer> lua vim.lsp.buf.clear_references()
to
autocmd CursorHold * lua vim.lsp.buf.document_highlight()
autocmd CursorMoved * lua vim.lsp.buf.clear_references()
Hi there! Thanks for putting this together, it has helped immensely :smile:
I'm currently working on a rather large project with multiple tsconfigs in the same project (different dirs tho). I bring this up because the following issue only comes up in this setup. Other
ts
projects work just fine, so there is a chance it has nothing to do with the config.That being said, temporarily swapping my config for the one in this repo and opening
ts
files in the problematic project produces the same outcome. So there's that :shrug:The project is also big. As in 1.5GB (without
node_modules
) kinda big.Basically, (after a small delay after opening a file) I get a recurring error:
This keeps popping up constantly which prevents me from doing anything.
Trying to run something like
:Telescope lsp_code_actions
just repeats part of the previous error:Might be worth mentioning that I occasionally get the following error:
For example, when editing my
init.vim
(even though there's just vimls and null-ls)I noticed that removing the line with
autocmd CursorHold <buffer> lua vim.lsp.buf.document_highlight()
(located in thehandlers.lua
file), gets rid of the first error message, although that still leaves the second one and simply means not having proper highlighting. So that didn't solve much...In case it helps, running
:LspInfo
with a problematic file open shows:And
:checkhealth
shows:Thanks in advance to anyone willing to shed some light on the situation!