Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add prefix key for keybindings of Windows Terminal actions #14387

Closed
leonasdev opened this issue Nov 14, 2022 · 2 comments
Closed

Add prefix key for keybindings of Windows Terminal actions #14387

leonasdev opened this issue Nov 14, 2022 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@leonasdev
Copy link

Description of the new feature/enhancement

Windows Terminal currently cannot set a prefix key (like tmux's Ctrl+b) that can trigger actions. In this case, terminal keystrokes may conflict with keystrokes from other applications inside the terminal.

Use case:
The user wants to move focus right by using the following keystrokes: Press Ctrl+b then press }.

Proposed technical implementation details (optional)
@leonasdev leonasdev added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 14, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 14, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1334 for more discussion.

/dup #1334

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Nov 14, 2022
@ghost
Copy link

ghost commented Nov 14, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Nov 14, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 14, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @leonasdev