-
Notifications
You must be signed in to change notification settings - Fork 8
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
LSP client not found #13
Comments
FWIW Subsequent key combos after the error all appear to work. |
Should be fixed. |
I can confirm that after updating this is fixed. Quick question before I close this out, what was the expected functionality that I was missing by not having |
|
Is there any chance that you will support other LSP integrations like coc.vim in the future? |
I updated the comment. LspDocumentSymbols() should work. Other LSP clients can be supported only if their APIs are exported. I use yegappan lsp, so it is no 'extra work' for me to look into issues. I can also make changes to yegappan lsp since I know the codebase quite well. Other Lsp's are extra work only because I do not know the codebase and it is not pleasant wading through legacy script (unlike vim9script). |
Thanks for all your help! And for putting this plugin together! I had been looking for how to get grep-like functionality from CTRLP for a long time. This plugin is a huge leap forward for me! |
Whenever I try to launch scope.vim from a key binding (
nnoremap <C-p> <scriptcmd>vim9cmd scope#fuzzy#File()<CR>
)I get the following error and no modal dialog appearsThis appears to come from
But I can't see anything that sets
g:loaded_lsp
. I did notice from the readme a link to https://github.com/yegappan/lsp so maybe it comes from there? However, I don't see in the requirements section that this is something that is required.Additionally, I already use
coc.vim
for this purpose and would prefer not to use https://github.com/yegappan/lsp if at all possible.The text was updated successfully, but these errors were encountered: