Navigate cmd history with up/down by default #1112
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
Limero
force-pushed
the
navigate-cmd-history-with-up-down
branch
from
22a40c4
to
c5e0f7f
Compare
|
Temporary solution I use in my |
|
Yes, I think the title is missing the words "by default". This is certainly already possible as @avioli pointed out. |
Limero
changed the title
|
You're right! I changed the title. I've had the same cmap in my lfrc for years and it makes sense that it's made the default, since the up/down keys are not bound to anything else in command mode. |
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.
This makes it possible to navigate history in command mode with the up and down arrow keys, which replicates the behavior of VIM.