starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: global hotkey to re-run last command #3942

New Issue
Open
opened 2026-01-30 23:33:55 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:33:55 +00:00
Owner
Copy Link

Originally created by @Christilut on GitHub (Sep 19, 2019).

Description of the new feature/enhancement

I would really like to see the ability to bind a global hotkey to repeat the last command in the visible terminal. In essence all it does is: up arrow and enter on the terminal that is visible. Should work even when terminal has no focus since I'm pressing this global hotkey when I'm not in the terminal.

Global hotkeys should be bindable to any key, including special keys such as Scroll Lock, Pause/Break and the Context Menu (the button next to the right CTRL).

iTerm2 has this functionality and no other terminal emulator I've tried has this, on Linux or Windows. I'm sure this is achievable with AutoHotkey but I'd prefer native functionality.

Use case for me:
When testing or running experimental scripts, it is common to rerun your script every time you make a change. It is very productive for me if I don't need to take my hands off the keyboard for this. Personally I would bind this functionality to the "context menu" key (between CTRL and Windows), since I never use that button anyway.

Originally created by @Christilut on GitHub (Sep 19, 2019). # Description of the new feature/enhancement I would really like to see the ability to bind a global hotkey to repeat the last command in the visible terminal. In essence all it does is: `up arrow` and `enter` on the terminal that is visible. Should work even when terminal has no focus since I'm pressing this global hotkey when I'm not in the terminal. Global hotkeys should be bindable to any key, including special keys such as Scroll Lock, Pause/Break and the Context Menu (the button next to the right CTRL). iTerm2 has this functionality and no other terminal emulator I've tried has this, on Linux or Windows. I'm sure this is achievable with AutoHotkey but I'd prefer native functionality. Use case for me: When testing or running experimental scripts, it is common to rerun your script every time you make a change. It is very productive for me if I don't need to take my hands off the keyboard for this. Personally I would bind this functionality to the "context menu" key (between CTRL and Windows), since I never use that button anyway.
claunia added the Issue-FeatureHelp WantedProduct-TerminalArea-UserInterface labels 2026-01-30 23:33:55 +00:00
claunia commented 2026-01-30 23:33:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 19, 2019):

Okay so what you're actually asking for is two things:

  • Global hotkeys that can be bound to Keybindings/ShortcutActions
  • A ShortcutAction that can send input to the terminal

The second part I've already discussed as a part of #2046, so I'm not gonna delve into that too far. I think that's a fine idea, and I'm totally on board. Might need some modification to support VKEYs as input, not just characters, but we can work that out.

The first part might be trickier. It certainly plays into discussion being had in #653. My real question is this: if you have multiple Terminal windows open, which one should the hotkey activate? Do they all get the hotkey's activation?

I'd be worried that this is dependent upon having #2080 and it's associated work finished, as we'll need to have a single manager process to be able to send global hotkeys to, that can then dispatch them to the appropriate Terminal instance.

@zadjii-msft commented on GitHub (Sep 19, 2019): Okay so what you're actually asking for is two things: * Global hotkeys that can be bound to Keybindings/ShortcutActions * A ShortcutAction that can send input to the terminal The second part I've already discussed as a part of #2046, so I'm not gonna delve into that too far. I think that's a fine idea, and I'm totally on board. Might need some modification to support VKEYs as input, not just characters, but we can work that out. The first part might be trickier. It certainly plays into discussion being had in #653. My real question is this: if you have multiple Terminal windows open, which one should the hotkey activate? Do they all get the hotkey's activation? I'd be worried that this is dependent upon having #2080 and it's associated work finished, as we'll need to have a single manager process to be able to send global hotkeys to, that can then dispatch them to the appropriate Terminal instance.
claunia commented 2026-01-30 23:33:56 +00:00
Author
Owner
Copy Link

@Christilut commented on GitHub (Sep 19, 2019):

Yes that sounds exactly right.

To answer your question: I'd expect the terminal that was last focused to receive the signal.

There might be use cases for sending the signal to all terminals, perhaps this can be a setting. But I think it would be intuitive to send it to the last focused terminal by default.

@Christilut commented on GitHub (Sep 19, 2019): Yes that sounds exactly right. To answer your question: I'd expect the terminal that was last focused to receive the signal. There might be use cases for sending the signal to all terminals, perhaps this can be a setting. But I think it would be intuitive to send it to the last focused terminal by default.
claunia commented 2026-01-30 23:33:56 +00:00
Author
Owner
Copy Link

@nofunatall commented on GitHub (Sep 30, 2019):

How would this work if you have a heavily modified bash profile?
i.e you've changed what up arrow does

@nofunatall commented on GitHub (Sep 30, 2019): How would this work if you have a heavily modified bash profile? i.e you've changed what up arrow does
claunia commented 2026-01-30 23:33:56 +00:00
Author
Owner
Copy Link

@Christilut commented on GitHub (Sep 30, 2019):

If the terminal can just send in the up arrow key command then it's up to bash to decide what to do with it.
I think if a user modifies their bash like this then they would expect this global hotkey to execute whatever normally happens when they physically press the up arrow button.

But this would be configurable in whatever way the user requires with #2046

@Christilut commented on GitHub (Sep 30, 2019): If the terminal can just send in the up arrow key command then it's up to bash to decide what to do with it. I think if a user modifies their bash like this then they would expect this global hotkey to execute whatever normally happens when they physically press the up arrow button. But this would be configurable in whatever way the user requires with #2046
claunia commented 2026-01-30 23:33:56 +00:00
Author
Owner
Copy Link

@fishzle commented on GitHub (Feb 15, 2020):

Are there any concerns with input-stealing? Or focus-stealing?
I'm thinking about how this feature sounds similar to the magic sysrq key in linux.
Another thought is that in a single-user environment, it's possibly safe, but in a multi-user/VM/docker environment, could this be unsafe?

@fishzle commented on GitHub (Feb 15, 2020): Are there any concerns with input-stealing? Or focus-stealing? I'm thinking about how this feature sounds similar to the magic sysrq key in linux. Another thought is that in a single-user environment, it's possibly safe, but in a multi-user/VM/docker environment, could this be unsafe?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Help Wanted Issue-Feature Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3942
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?