fix: E684: List index out of range: 0 #1481
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
prabirshrestha
force-pushed
the
fuyg/dev
branch
from
4589d7e
to
2634a62
Compare
|
Merged. Thanks! |
|
@prabirshrestha @FuDesign2008 I don't have time now to log a proper bug report, but for me I get weird errors sometimes, with plain Vim 8.2, apparently because that does not have the The error looks similar, also around One workaround is to disable vim-lsp-settings; the other is for now to use the pre-October-10 version. :-) Note that going back to 7233bb2 doesn't give any (Thanks for all this Vim LSP work by the way, very much appreciated!) |
ompugao
pushed a commit
to ompugao/vim-lsp
that referenced
this pull request
Dec 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix bug like below:
