starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Pause and resume execution of left- and right-click like in PowerShell #21623

New Issue
Closed
opened 2026-01-31 07:49:56 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 07:49:56 +00:00
Owner
Copy Link

Originally created by @github-account1111 on GitHub (May 2, 2024).

Description of the new feature/enhancement

I googled and searched through issues but couldn't find anything about this.

On Windows 10 I could left-click anywhere inside the PowerShell window, and the execution would pause. I knew the execution was paused when the title bar said "Select PowerShell." When I was ready to resume the execution I just needed to right-click anywhere on the window.

This incredibly handy feature seems to be missing in Microsoft Terminal's PowerShell on Windows 11. Now I have to either wait for the execution to finish (which depending on what I'm running could take hours) or cancel it entirely.

Proposed technical implementation details (optional)

Same as on Windows 10.

Originally created by @github-account1111 on GitHub (May 2, 2024). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> I googled and searched through issues but couldn't find anything about this. On Windows 10 I could left-click anywhere inside the PowerShell window, and the execution would pause. I knew the execution was paused when the title bar said "Select PowerShell." When I was ready to resume the execution I just needed to right-click anywhere on the window. This incredibly handy feature seems to be missing in Microsoft Terminal's PowerShell on Windows 11. Now I have to either wait for the execution to finish (which depending on what I'm running could take hours) or cancel it entirely. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> Same as on Windows 10.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 07:49:56 +00:00
claunia commented 2026-01-31 07:49:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 2, 2024):

Is the end goal here to actually suspend the CLI application that's running connected to the Terminal, or just make it easier to select text in the scrollback/?

There's some related discussion in:

@zadjii-msft commented on GitHub (May 2, 2024): Is the end goal here to actually suspend the CLI application that's running connected to the Terminal, or just make it easier to select text in the scrollback/? There's some related discussion in: * #980 * #408
claunia commented 2026-01-31 07:50:00 +00:00
Author
Owner
Copy Link

@github-account1111 commented on GitHub (May 2, 2024):

It's the former. It's strange to me that most participants of those issues seem to only be interested in the latter.

Especially that second one. It's not a bug, it's the default PowerShell behavior. It doesn't "freeze." As I mentioned in the description, you can easily tell if it's active or not by looking at the title bar.

@github-account1111 commented on GitHub (May 2, 2024): It's the former. It's strange to me that most participants of those issues seem to only be interested in the latter. Especially that second one. It's not a bug, it's the default PowerShell behavior. It doesn't "freeze." As I mentioned in the description, you can easily tell if it's active or not by looking at the title bar.
claunia commented 2026-01-31 07:50:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 2, 2024):

Well, it's technically correct that it doesn't "freeze". But selecting in the vintage console prevents conhost from servicing any further console API calls. It just blocks the call until the selection is dismissed. That effectively pauses powershell (or any other CLI app) that's waiting on writing before continuing.

I'm guessing for most people (myself included) are just happy that selecting the Terminal accidentally doesn't entirely pause long builds anymore. I could have sworn there was an issue floating around asking for the ability to manually pause the conpty client, but I can't find anything like that now...

@zadjii-msft commented on GitHub (May 2, 2024): Well, it's technically correct that it doesn't "freeze". But selecting in the vintage console prevents conhost from servicing any further console API calls. It just blocks the call until the selection is dismissed. That effectively pauses powershell (or any other CLI app) that's waiting on writing before continuing. I'm guessing for most people (myself included) are just happy that selecting the Terminal accidentally doesn't entirely pause long builds anymore. I could have sworn there was an issue floating around asking for the ability to manually pause the conpty client, but I can't find anything like that now...
claunia commented 2026-01-31 07:50:01 +00:00
Author
Owner
Copy Link

@github-account1111 commented on GitHub (May 2, 2024):

What's the issue with that behavior? You can just right-click to resume. Takes less than a second. Meanwhile potentially hours are wasted waiting for execution to finish, or execution has to be cancelled entirely. It also helps avoid overheating, especially if you use laptops or external drives.

You're basically eliminating a tiny little inconvenience (I even struggle to call it that, it's that inconsequential so long as you bother to look at the title bar) at the cost of quite a lot of fundamental functionality and usefulness.

@github-account1111 commented on GitHub (May 2, 2024): What's the issue with that behavior? You can just right-click to resume. Takes less than a second. Meanwhile potentially hours are wasted waiting for execution to finish, or execution has to be cancelled entirely. It also helps avoid overheating, especially if you use laptops or external drives. You're basically eliminating a tiny little inconvenience (I even struggle to call it that, it's that inconsequential so long as you bother to look at the title bar) at the cost of quite a lot of fundamental functionality and usefulness.
claunia commented 2026-01-31 07:50:01 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 2, 2024):

Maybe you already know, but...

Actually you can still pause the output at any time: Just press the "Pause" or "Break" key. 😅 Almost all modern hardware and operating systems use the Pause/Break key for pausing terminal output. It's usually in the top right, above the Delete and Insert keys, if you have a full sized keyboard. If you don't have a Pause/Break key you can press Ctrl+S instead. On the latest Windows Terminal versions both should pause/freeze the output immediately until you press another key.

If you did already know that the Pause key does this, can you explain why it doesn't work for you?

@lhecker commented on GitHub (May 2, 2024): Maybe you already know, but... Actually you can still pause the output at any time: Just press the "Pause" or "Break" key. 😅 Almost all modern hardware and operating systems use the Pause/Break key for pausing terminal output. It's usually in the top right, above the Delete and Insert keys, if you have a full sized keyboard. If you don't have a Pause/Break key you can press Ctrl+S instead. On the latest Windows Terminal versions both should pause/freeze the output immediately until you press another key. If you did already know that the Pause key does this, can you explain why it doesn't work for you?
claunia commented 2026-01-31 07:50:02 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 2, 2024):

You're basically eliminating a tiny little inconvenience (I even struggle to call it that, it's that inconsequential so long as you bother to look at the title bar) at the cost of quite a lot of fundamental functionality and usefulness.

Oh and... For what it's worth, I'm personally not opposed to implementing your suggestion, and I think you make an excellent argument for this feature. In fact I often did this myself (selecting to pause output), before I learned that the Pause key can be used for this.

However, we currently can't easily implement it correctly for architectural reasons (the entire ConPTY setup). It's certainly possible, for instance by sending a pause key press when selection starts and when it ends, but that's obviously going to be very error prone. For example, if someone had already paused output, or if we miss a key press somehow, or someone injects the pause key via the console APIs, in all those cases the thing the PTY sees and what Windows Terminal sees would get out of sync and you'd never be able to properly unpause the output anymore.

Given that other terminals don't seem to have this behavior, nor make it configurable, and that virtually all terminals support the Pause key and its Ctrl+S alias, I think this feature request may be too risky in my personal opinion.

@lhecker commented on GitHub (May 2, 2024): > You're basically eliminating a tiny little inconvenience (I even struggle to call it that, it's that inconsequential so long as you bother to look at the title bar) at the cost of quite a lot of fundamental functionality and usefulness. Oh and... For what it's worth, I'm personally not opposed to implementing your suggestion, and I think you make an excellent argument for this feature. In fact I often did this myself (selecting to pause output), before I learned that the Pause key can be used for this. However, we currently can't easily implement it correctly for architectural reasons (the entire ConPTY setup). It's certainly possible, for instance by sending a pause key press when selection starts and when it ends, but that's obviously going to be very error prone. For example, if someone had already paused output, or if we miss a key press somehow, or someone injects the pause key via the console APIs, in all those cases the thing the PTY sees and what Windows Terminal sees would get out of sync and you'd never be able to properly unpause the output anymore. Given that other terminals don't seem to have this behavior, nor make it configurable, and that virtually all terminals support the Pause key and its Ctrl+S alias, I think this feature request may be too risky in my personal opinion.
claunia commented 2026-01-31 07:50:02 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (May 8, 2024):

Thanks for the feedback. As stated above, this is a bit risky of a change and the desired behavior should be accessible via the Pause key and its Ctrl+S alias. Closing 😊

@carlos-zamora commented on GitHub (May 8, 2024): Thanks for the feedback. As stated above, this is a bit risky of a change and the desired behavior should be accessible via the Pause key and its Ctrl+S alias. Closing 😊
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 Issue-Feature Needs-Attention Needs-Tag-Fix Needs-Triage
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#21623
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?