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

Support sending f13-f24 #6342

Closed
mb1337 opened this issue Jun 3, 2020 · 3 comments
Closed

Support sending f13-f24 #6342

mb1337 opened this issue Jun 3, 2020 · 3 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

@mb1337
Copy link

mb1337 commented Jun 3, 2020

Description of the new feature/enhancement

Some programs use extra function keys, f13, f14, f15, etc. I haven't found a way to enter these into windows terminal. In puTTY it's shift+f5 to get f15, etc.

Proposed technical implementation details (optional)

Allow mapping keys in settings.json

{ "command": { "action": "mapKey", "key": "f15"}, keys: "shift+f5" }

I want to be able to send function keys that are not on a standard keyboard (f13-f24) to a terminal application.

@mb1337 mb1337 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 3, 2020
@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 Jun 3, 2020
@DHowett
Copy link
Member

DHowett commented Jun 5, 2020

Thanks for the request! I'm going to track this one with /dup #3799, which will allow you to bind any keyboard shortcut to any string. This will let you send the encoded forms of F13-F24.

@ghost
Copy link

ghost commented Jun 5, 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 Jun 5, 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 Jun 5, 2020
@mb1337
Copy link
Author

mb1337 commented Jun 5, 2020

I tried to use AutoHotkey as a workaround but it doesn't seem to be getting through.
+F3::SendInput, {F13}
I've also tried cmd and PowerShell. Those don't work either so I think the problem lies a bit deeper.
It does work in puTTY and git bash (but not bash.exe launched from a tab profile).

Windows Terminal
Version: 1.0.1401.0

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