-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
LspNextError and LspPreviousError not working #173
Comments
It might be worth exploring to populate the quickfix list automatically, instead of using LspNextError. |
Yes, I'd also appreciate if Quickfix were populated automatically. And I also report LspNextError and co do not work. |
This appears to be working for me on the latest verion. @phcerdan Can you confirm?
This might be confusing to do out of the box as the quickfix can be used for a number of things. What about adding this to your autocmd CursorHold call lsp#ui#vim#diagnostics#document_diagnostics() |
Please try the latest master. It should be working now. |
LspNextError
andLspPreviousError
does not work for me, either with errors or with warnings.I use
:LspDocumentDiagnostics
and then navigate with:cnext
:cprevious
or]q
[q
if using vim-unimpairedRelated: #171
The text was updated successfully, but these errors were encountered: