fix: publishing move events to other nvim plugins #821
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
Hopefully this will improve the stability in the lsp tests. mikavilpas/tui-sandbox#351
It would silently crash when trying to publish move events to other nvim plugins. I don't think this is a huge issue since the feature does not seem to be widely used. It might be that it never actually worked for move events, but did work for rename and bulk events. For a description of this event publishing feature, see #495
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: publishing move events to other nvim plugins
It would silently crash when trying to publish move events to other nvim
plugins. I don't think this is a huge issue since the feature does not
seem to be widely used.
It might be that it never actually worked for move events, but did work
for rename and bulk events.
For a description of this event publishing feature, see
#495