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.

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

Unbind all default shortcuts #15277

Closed
KMPrg opened this issue May 3, 2023 · 4 comments
Closed

Unbind all default shortcuts #15277

KMPrg opened this issue May 3, 2023 · 4 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

@KMPrg
Copy link

KMPrg commented May 3, 2023

Description of the new feature/enhancement

Provides settings for unbinding all default shortcuts at once

Windows terminal is good software,
but it has too many keyboard shortcuts by default,
when using an editor like VIM, there are a lot of shortcut key conflicts,
want to give the user custom keyboard options, so there will not be a lot of inexplicable keyboard shortcuts conflict.

Proposed technical implementation details (optional)

In setting. JSON file, provide a set of all the default keyboard shortcuts can be disabled at one time,
so that users can easily customize the keyboard shortcuts, the need to manually configure their own keyboard shortcuts,
avoid confusing keyboard shortcuts

@KMPrg KMPrg added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 3, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added 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 May 3, 2023
@zadjii-msft
Copy link
Member

I think our plan has been to add support for "keymaps". This would follow the work for #6899. Then, keymaps would contain objects which bind keys to various actions. The user could then just specify keymap: "foo" to replace all their keybindings with the ones in foo, no layering involved. Adding keys to actions directly would just update the "default" keymap, which is used when no keymap is specified. Unbinding everything would be something like "keymap": null

I think for tracking purposes, it's best to just merge this with that thread. Thanks!

/dup #2205

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 May 3, 2023
@KMPrg
Copy link
Author

KMPrg commented May 9, 2023

@zadjii-msft @microsoft-github-policy-service
Thank you very much for your answers. I carefully read the issue you provided and #3483 .
I think I may have misunderstood, the main problem does not seem to be the keybindings, but something more complex.

For example, the behavior of ctrl+., even if I use unbund or null to unbind in .json, it will still play the role of moving the cursor to the next line in vim or Emacs. I am sure I have not set this shortcut key, and If you don't use vim or Emacs in the Windows terminal, you don't have these weird default keybindings.

These shortcut keys that cannot be unbound cause shortcut key conflicts when using vim and emacs editors. And there doesn't seem to be any viable solution.

@hvesalai
Copy link

Having the same problem. Just installed Ubuntu-22 and I use emacs.

I would need to have a way to remove all WIndows Terminal bindings so that emacs would receive the keycodes. I don't need much from Windows Terminal, so I'm happy not having any bindings for it. For me it is important that all keycodes go through.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants