Fix 'No matching autocommands' warning caused by #437#440
Merged
haya14busa merged 2 commits intoeasymotion:masterfrom Dec 17, 2020
n-p-e:master
Merged
Fix 'No matching autocommands' warning caused by #437#440haya14busa merged 2 commits intoeasymotion:masterfrom n-p-e:master
haya14busa merged 2 commits intoeasymotion:masterfrom
n-p-e:master
Conversation
|
Thank you for fixing this. I have been using your branch for a week now and it's working great 👍. I would enable this by default to be honest, if user has |
Member
|
Sry for the late response. |
Contributor
Author
Done. |
Member
|
Thanks! 👍 |
|
Seems these user events I find another guy got annoyed by the modeline parsing thing too. Pitfall of Vim: :doautocmd triggers modeline processing |
This file contains hidden or 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
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.
The warning only appears in Vim. I only tested on Neovim and did not notice the warning. It is fixed now.
I'm sorry for the mess.