Recognise more modes #3
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
|
thanks, I'm not sure whether or not I have run into any of these but I suspect I will at some point. makes me think it may be worth me looking into all of the additional mode combinations like that that can be reported from the rpc query and adding support for them |
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.
Recognize "insert normal" and "insert completion" modes. Without insert competition, vim would sometimes think it is in normal mode even though it is in insert mode (tested with youcompleteme) and emit an i. I suspect I added the inside normal mode after it triggered some of my asserts and not because of some functional thing, but adding it shouldn't hurt anyway.