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

Feature request: allow keyboard input while an app is running #5171

New Issue
Closed
opened 2026-01-31 00:06:41 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:06:41 +00:00
Owner
Copy Link

Originally created by @mikemaccana on GitHub (Nov 25, 2019).

Description of the new feature/enhancement

Sometimes, as a shell user, I just want some space before some app is about to log something interesting, as a kind of visual marker, so what's appear doesn't get lost in the noise.

Unix folk often just bang enter to do this, but the console and Windows Terminal seem to take keyboard control away when an app is running

It would be useful to allow this as an option.

Originally created by @mikemaccana on GitHub (Nov 25, 2019). # Description of the new feature/enhancement Sometimes, as a shell user, I just want some space before some app is about to log something interesting, as a kind of visual marker, so what's appear doesn't get lost in the noise. Unix folk often just bang enter to do this, but the console and Windows Terminal seem to take keyboard control away when an app is running It would be useful to allow this as an option.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 00:06:41 +00:00
claunia commented 2026-01-31 00:06:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 25, 2019):

I don't really think this is a terminal problem, this might just be more of a commandline client issue.

If I run ping bing.com in conhost or the Terminal, I can definitely still use enter to separate the lines of output easily. ping.exe -t bing.com however eats the keystrokes.

Since this is something that each client seems to handle in their own way, I'm not sure there's a way for us to be able to solve that without breaking compatibility...

@zadjii-msft commented on GitHub (Nov 25, 2019): I don't really think this is a _terminal_ problem, this might just be more of a commandline client issue. If I run `ping bing.com` in conhost or the Terminal, I can definitely still use enter to separate the lines of output easily. `ping.exe -t bing.com` however eats the keystrokes. Since this is something that each client seems to handle in their own way, I'm not sure there's a way for us to be able to solve that without breaking compatibility...
claunia commented 2026-01-31 00:06:42 +00:00
Author
Owner
Copy Link

@mikemaccana commented on GitHub (Nov 25, 2019):

@zadjii-msft You can? bing.com doesn't respond to ICMP for me, but more importantly, if I try a site that does respond, using enter does not separate the lines of output:

 ping google.com

Pinging google.com [172.217.169.46] with 32 bytes of data:
Reply from 172.217.169.46: bytes=32 time=6ms TTL=56
(bangs enter a lot here and nothing happens)
Reply from 172.217.169.46: bytes=32 time=6ms TTL=56
...

I actually asked about it on the Powershell slack, and they thought it was terminal / conhost thing. 😂

@mikemaccana commented on GitHub (Nov 25, 2019): @zadjii-msft You can? `bing.com` doesn't respond to ICMP for me, but more importantly, if I try a site that *does* respond, using enter does not separate the lines of output: ``` ping google.com Pinging google.com [172.217.169.46] with 32 bytes of data: Reply from 172.217.169.46: bytes=32 time=6ms TTL=56 (bangs enter a lot here and nothing happens) Reply from 172.217.169.46: bytes=32 time=6ms TTL=56 ... ``` I actually asked about it on the Powershell slack, and they thought it was terminal / conhost thing. 😂
claunia commented 2026-01-31 00:06:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 25, 2019):

Okay so I may have tried with another search engine that did respond to ping, and then edited my post assuming bing.com would work 😆

I may have also accidentally forgotten an important piece of info: WSL ping works, but ping.exe does not:

WSL ping:
image

You can see the spots where I hit enter a bunch in the middle of ping

ping.exe:
image

Here you can see cmd.exe processing all the enters from while I was running ping.exe all at the end

@zadjii-msft commented on GitHub (Nov 25, 2019): Okay so I may have tried with _another search engine_ that _did_ respond to `ping`, and then edited my post assuming `bing.com` would work 😆 I may have also accidentally forgotten an important piece of info: __WSL__ `ping` works, but `ping.exe` does _not_: WSL ping: ![image](https://user-images.githubusercontent.com/18356694/69566414-a95c9600-0f7c-11ea-91f7-8969f0d7e6ee.png) You can see the spots where I hit enter a bunch in the middle of ping `ping.exe`: ![image](https://user-images.githubusercontent.com/18356694/69566458-c1341a00-0f7c-11ea-9038-6f97c0faceb3.png) Here you can see cmd.exe processing all the enters from while I was running `ping.exe` all at the end
claunia commented 2026-01-31 00:06:42 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 25, 2019):

The core of the issue here is that on the unix/linux tty subsystem, standard input is in echo mode by default. Even when an application isn't reading, the tty will echo back all of your input.

The console subsystem defaults to echo off, but the application is still receiving the events. For heaps of reasons, most of which are compatibility and user expectations around input, we're not going to be changing that. Sorry!

/resolution-answered

@DHowett-MSFT commented on GitHub (Nov 25, 2019): The core of the issue here is that on the unix/linux tty subsystem, standard input is in echo mode by default. Even when an application isn't reading, the tty will echo back all of your input. The console subsystem defaults to echo _off_, but the application is still receiving the events. For heaps of reasons, most of which are compatibility and user expectations around input, we're not going to be changing that. Sorry! /resolution-answered
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-Question Needs-Tag-Fix Resolution-Answered
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#5171
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?