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

Being able to bind any key actions to other keys #5812

Closed
mutageneral opened this issue May 8, 2020 · 2 comments
Closed

Being able to bind any key actions to other keys #5812

mutageneral opened this issue May 8, 2020 · 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

@mutageneral
Copy link

mutageneral commented May 8, 2020

Description of the new feature/enhancement

When I browse man pages I have to use the arrow keys to move up and down and it's slow. So I wanted to bind shift+mouceweelUP to arowkeyUP but you cannot bind keys to other keys. The command (referring to the command property of the keybindings, not a command entered in a cli) the arrow keys trigger when they are pressed is not available to be assigned to other keys. I also didn't find any way to bind something to the mouse-wheel in https://github.com/microsoft/terminal/blob/master/doc/cascadia/SettingsSchema.md#keys

Proposed (not so)technical implementation "details"

Add all the commands/actions that keys can trigger and add all the keys (and other inputs like a mouse wheel) you could possibly bind things to.

@mutageneral mutageneral added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 8, 2020
@ghost ghost 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 8, 2020
@DHowett-MSFT
Copy link
Contributor

Thanks for the request! I think your request will be solved by combining #1553 and #3799, when they're done.

However, I think your actual bug is a /dupe of #381. The pager that man uses typically enables the alternate buffer mode, and then it enables a "mouse cursor keys" mode that translates your mouse wheel automatically into up/down commands.

Because Terminal is not aware that the "alternate buffer" mode is turned on, it doesn't have the right mouse wheel behavior in the pager.

@ghost
Copy link

ghost commented May 8, 2020

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 May 8, 2020
@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 May 8, 2020
This issue was closed.
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

2 participants