You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I love your plugin btw. But if I get the LSP references and the list is quite big (+100 references), the quickfix renders slower. Maybe we could add an option that disables the treesitter highlight if the list is 50+ elements.
:-)
Provide background
No response
What is the significance of this feature?
nice to have
Additional details
No response
The text was updated successfully, but these errors were encountered:
Could you be a bit more specific about the problem you are seeing? Does the quickfix buffer take longer to open? Is it causing Neovim to be laggy? Is it just taking a while to highlight?
I made the highlighting (both treesitter and LSP) async with the intention that highlighting might take longer for long lists, but it shouldn't block the UI and ideally won't add much lag (some lag is unavoidable).
UPDATE: the buggy behavior I was experiencing has disappeared. Here is what happend: open a project, change to a subdirectory, make some search and put the files into a quickfix list. Initally, the quickfix list has the correct file paths and the highlight works. If I close the session and reopens again, the file paths of the quickfix list are not correct: they were relative to that subdirectory but now they are relative to the project directory, thus are inexisting files. This is what caused the bug... But this depends on how the session is saved (I have to figure it out, it is handled by other plugin)
Did you check existing requests?
Describe the feature
Hello. I love your plugin btw. But if I get the LSP references and the list is quite big (+100 references), the quickfix renders slower. Maybe we could add an option that disables the treesitter highlight if the list is 50+ elements.
:-)
Provide background
No response
What is the significance of this feature?
nice to have
Additional details
No response
The text was updated successfully, but these errors were encountered: