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

Make Actions (Keyboard Shortcut Mappings) Configurable per Profile #11624

Closed
christophehad opened this issue Oct 27, 2021 · 2 comments
Closed

Make Actions (Keyboard Shortcut Mappings) Configurable per Profile #11624

christophehad opened this issue Oct 27, 2021 · 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

@christophehad
Copy link

christophehad commented Oct 27, 2021 •
edited by zadjii-msft
Loading

Description of the new feature/enhancement

Problem: I love using multiple profiles on Windows Terminal. Since I use WSL (Ubuntu) and Vim, I disabled the Ctrl+v mapping (pasting) from Actions to avoid conflicts with Vim's Ctrl+v (Visual Block). However, I'm always erroneously pressing Ctrl+v when trying to paste in other profiles (cmd, PowerShell). I would like to be able to change Actions (keyboard shortcuts) per profile, which would increase our productivity.
A clear and concise description of what the problem is that the new feature would solve.

Proposed technical implementation details (optional)

Make the settings.json file (or a new keyboard mappings json file) specific to each profile, by getting inspire from VS Code.
@christophehad christophehad added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 27, 2021
@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 Oct 27, 2021
@zadjii-msft
Copy link
Member

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

/dup #5790

@ghost
Copy link

ghost commented Oct 27, 2021

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 Oct 27, 2021
@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 Oct 27, 2021
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 @christophehad