Fix terminal-mode re-enabling after escape - #256
Merged
Merged
Conversation
Co-authored-by: Shougo <41495+Shougo@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
Shougo
September 9, 2026 03:36
View session
Shougo
marked this pull request as ready for review
September 9, 2026 03:36
Shougo
approved these changes
Sep 9, 2026
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.
When skkeleton is used in terminal mode, re-enabling after
<Esc>could be routed through theescapestate instead of the enable path, leaving skkeleton inactive. PR #252 removed the resulting error but did not restore activation.enableto proceed directly when the current state isescape.escapestate in terminal mode.