Proof-of-concept for queuing multiple actions on keybindings - #86
Draft
arkonger wants to merge 1 commit into
Draft
Proof-of-concept for queuing multiple actions on keybindings#86arkonger wants to merge 1 commit into
arkonger wants to merge 1 commit into
Conversation
8 tasks
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.
Summary
Added support for queuing multiple actions on a keybinding by setting the keybinding's
actionto an array of strings.Motivation
This is just a proof-of-concept I threw together and will definitely need more testing before merging, but I think it would be quite helpful. As I've configured my keybindings, I've found that I've often had to spawn
bash -cto pass several commands throughumbriel msg, which makes me think that something like this would be useful not just for myself but for others as well. I thought it was worth submitting to see if this is a feature the team is interested in before I put more effort into testing.Type of Change
Testing
I've only done minimal testing so far, by setting
"Mod+Slash" = { action = ["workspace-next", "spawn:kitty"], repeat = false }and then testing in a nested session.Manual Coverage
Checklist
SCOPE.md, or its scope was agreed in an issue or on Discord first.CONTRIBUTING.md.just format, or this PR has no C++ changes.docs/andexamples/config.toml, or this PR does not change user-facing configuration or behavior.