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

terminal output freezes on click #621

New Issue
Closed
opened 2026-01-30 21:57:13 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 21:57:13 +00:00
Owner
Copy Link

Originally created by @kunwon1 on GitHub (Apr 10, 2019).

This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: (Type ver at a Windows Command Prompt) 10.0.17134.648

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Tailing a log file, the screen is continuously scrolling, I click on the terminal window and output freezes until ESC is pressed

  • What's wrong / what should be happening instead: Output should continue regardless of clicking on the terminal window

I see this issue that was closed, it references this repo, but I cannot find a corresponding issue
https://github.com/Microsoft/WSL/issues/1223

Originally created by @kunwon1 on GitHub (Apr 10, 2019). This bug-tracker is monitored by Windows Console development team and other technical types. **We like detail!** If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). > **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: (Type `ver` at a Windows Command Prompt) 10.0.17134.648 * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Tailing a log file, the screen is continuously scrolling, I click on the terminal window and output freezes until ESC is pressed * What's wrong / what should be happening instead: Output should continue regardless of clicking on the terminal window I see this issue that was closed, it references this repo, but I cannot find a corresponding issue https://github.com/Microsoft/WSL/issues/1223
claunia commented 2026-01-30 21:57:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 10, 2019):

You're right, this was closed in the WSL repo without creating a matching issue in this repo.

As stated in the original issue, this is a feature request for the console that's on the backlog.

@zadjii-msft commented on GitHub (Apr 10, 2019): You're right, this was closed in the WSL repo without creating a matching issue in this repo. As stated in the original issue, this is a feature request for the console that's on the backlog.
claunia commented 2026-01-30 21:57:15 +00:00
Author
Owner
Copy Link

@HBelusca commented on GitHub (Apr 27, 2019):

Is this happening because QuickEdit mode (in the console Properties dialog) was enabled?

@HBelusca commented on GitHub (Apr 27, 2019): Is this happening because QuickEdit mode (in the console Properties dialog) was enabled?
claunia commented 2026-01-30 21:57:15 +00:00
Author
Owner
Copy Link

@jcoutch commented on GitHub (May 8, 2019):

This is the same behavior as the current ConHost in Windows. If you click inside the window, it assumes you're attempting to select text, highlights a single character, and pauses execution of whatever process is in that window.

I can't tell you how much time I've wasted trying to debug applications running in a console window, getting mad at why it's not responding, just to find out I had one character selected in the terminal that was halting it's execution. 😭

@jcoutch commented on GitHub (May 8, 2019): This is the same behavior as the current ConHost in Windows. If you click inside the window, it assumes you're attempting to select text, highlights a single character, and pauses execution of whatever process is in that window. I can't tell you how much time I've wasted trying to debug applications running in a console window, getting mad at why it's not responding, just to find out I had one character selected in the terminal that was halting it's execution. 😭
claunia commented 2026-01-30 21:57:15 +00:00
Author
Owner
Copy Link

@HBelusca commented on GitHub (May 8, 2019):

I can't tell you how much time I've wasted trying to debug applications running in a console window, getting mad at why it's not responding, just to find out I had one character selected in the terminal that was halting it's execution.

Usually said console window prepends "Select " or "Mark " in front of its title.
I note that it's not done by the new windows-terminal. (Also selection by using only keyboard -- aka. "Mark" -- or in block-mode as done already by conhost would be welcome 😃 .)

@HBelusca commented on GitHub (May 8, 2019): > I can't tell you how much time I've wasted trying to debug applications running in a console window, getting mad at why it's not responding, just to find out I had one character selected in the terminal that was halting it's execution. Usually said console window prepends "Select " or "Mark " in front of its title. I note that it's not done by the new windows-terminal. (Also selection by using only keyboard -- aka. "Mark" -- or in block-mode as done already by conhost would be welcome 😃 .)
claunia commented 2026-01-30 21:57:16 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 18, 2019):

This is how conhost is supposed to work. Resolving.

@miniksa commented on GitHub (May 18, 2019): This is how conhost is supposed to work. Resolving.
claunia commented 2026-01-30 21:57:16 +00:00
Author
Owner
Copy Link

@kunwon1 commented on GitHub (May 24, 2019):

Does this text from the referenced issue no longer apply? Are there no longer plans to make this a configurable option?

We tried disabling it once on internal builds and were nearly overrun by angry engineers with pitchforks and burning torches! We do, however, hear you and agree that it should be a configurable behavior, and so have added this ask to our internal feature tracking system and will consider implementing in a future build.

https://github.com/Microsoft/WSL/issues/1223#issuecomment-391165898

@kunwon1 commented on GitHub (May 24, 2019): Does this text from the referenced issue no longer apply? Are there no longer plans to make this a configurable option? > We tried disabling it once on internal builds and were nearly overrun by angry engineers with pitchforks and burning torches! We do, however, hear you and agree that it should be a configurable behavior, and so have added this ask to our internal feature tracking system and will consider implementing in a future build. https://github.com/Microsoft/WSL/issues/1223#issuecomment-391165898
claunia commented 2026-01-30 21:57:16 +00:00
Author
Owner
Copy Link

@jcoutch commented on GitHub (May 24, 2019):

I'm also pretty sure the behavior of Terminal is inconsistent with the existing console in Windows. For example, if the window is un-focused, a single click on the console does not initiate select/mark. It only initiates select/mark when clicked while the window is focused. When I tried out Terminal a couple weeks ago, it was marking regardless of the windows current focus state.

@jcoutch commented on GitHub (May 24, 2019): I'm also pretty sure the behavior of Terminal is inconsistent with the existing console in Windows. For example, if the window is un-focused, a single click on the console **does not** initiate select/mark. It only initiates select/mark when clicked while the window is focused. When I tried out Terminal a couple weeks ago, it was marking regardless of the windows current focus state.
claunia commented 2026-01-30 21:57:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 24, 2019):

This issue is closed because it was promarily tracking the feature in the legacy conhost.exe. Since we're not planning on making this configurable in conhost.exe, we closed the issue. We do however plan on making it configurable in the Windows Terminal. I've moved that discussion to #980

@zadjii-msft commented on GitHub (May 24, 2019): This issue is closed because it was promarily tracking the feature in the legacy conhost.exe. Since we're not planning on making this configurable in conhost.exe, we closed the issue. We do however plan on making it configurable in the Windows Terminal. I've moved that discussion to #980
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-Interaction Issue-Feature Product-Conhost Resolution-By-Design
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#621
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?