fix: g waits for second keypress, gg works as two-key command#12
Merged
Conversation
12e8c61 to
ee3730d
Compare
g used to fire input.buffer.home on its own. Now sets pendingChar and waits. gg moves to buffer start, g+Escape or g+unknown cancels. Visual mode gg selects to buffer start.
ee3730d to
f3de7d5
Compare
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.
Bare
gno longer jumps to buffer start. It sets pending state and waits for the second key.ggmoves to top,g+Escape cancels. Works in visual mode too.Previously out of a technical constrain I used only
gto act as what vim users would expectggto do.I also added the option to extend to additional
g{char}commands likeg0etc, in the future.