mode/prompt-buffer: Add delete-backwards-word vi keybinding - #3194
Merged
aadcg merged 1 commit intoSep 28, 2023
Merged
Conversation
Member
|
@MaxGyver83, thank you for your interest! Your feedback and thoughts are always appreciated. |
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.
Description
Add missing
delete-backwards-wordvi keybinding toprompt-buffer.Discussion
Not much to discuss:
→ vim help
Checklist:
Everything in this checklist is required for each PR. Please do not approve a PR that does not have all of these items.
Git hygiene:
My code follows the style guidelines for Common Lisp code. See:
I have performed a self-review of my own code.
My code has been reviewed by at least one peer. (The peer review to approve a PR counts. The reviewer must download and test the code.)
Documentation:
:documentations written in the aforementioned style. (It's OK to skip the docstring for really trivial parts.)changelog.lispwith my changes if it's anything user-facing (new features, important bug fix, compatibility breakage).migration.lispentry for all compatibility-breaking changes.Compilation and tests:
(asdf:test-system :nyxt)and(asdf:test-system :nyxt/gi-gtk)) and they pass.