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
In theory one should be able to use treesitter to get the current scope attached to the cursor and filter search results based on that.
Do there exist any experiments with performance numbers based on that approach?
It is very frustrating to get completion results for things, which are never in scope (although only a lsp can rule this out in all cases for macro resolution).
The text was updated successfully, but these errors were encountered:
I tried setting the max_item_count to 5, and while it does limit the responses to 5 (which is good to avoid getting flooded with irrelevant values), the responses at the top don't seem any more likely to be from files that have the same filetype/extension as the current buffer.
The entry_filter option seemed like it might work, but neither entry nor ctx seem to include the information that pops up showing the file it originated from. If I was able to access just the originating file, I could compare the matching file extension against string.match(vim.fn.expand('%'), "[^%.]*$"), but maybe the data in that popup doesn't make it out of cmp-nvim-tags?
In theory one should be able to use treesitter to get the current scope attached to the cursor and filter search results based on that.
Do there exist any experiments with performance numbers based on that approach?
It is very frustrating to get completion results for things, which are never in scope (although only a lsp can rule this out in all cases for macro resolution).
The text was updated successfully, but these errors were encountered: