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

Question: TCSAFLUSH equivalent for Windows console host? #6892

New Issue
Open
opened 2026-01-31 00:49:50 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:49:50 +00:00
Owner
Copy Link

Originally created by @alexrp on GitHub (Mar 15, 2020).

Hello,

On Unix systems, when setting up a terminal for 'raw' processing, you have the option of passing TCSAFLUSH to tcsetattr(). The description of it is as follows:

the change occurs after all output written to the object referred by fd has been transmitted, and all input that has been received but not read will be discarded before the change is made.

This is quite convenient for certain types of applications since it means you won't get unexpected data back from reading stdin after you've made changes to terminal settings.

I'm wondering if there is an equivalent to this for the Windows console host when using SetConsoleMode()?

Originally created by @alexrp on GitHub (Mar 15, 2020). Hello, On Unix systems, when setting up a terminal for 'raw' processing, you have the option of passing `TCSAFLUSH` to `tcsetattr()`. The description of it is as follows: > the change occurs after all output written to the object referred by fd has been transmitted, and all input that has been received but not read will be discarded before the change is made. This is quite convenient for certain types of applications since it means you won't get unexpected data back from reading `stdin` after you've made changes to terminal settings. I'm wondering if there is an equivalent to this for the Windows console host when using `SetConsoleMode()`?
claunia added the Issue-FeatureProduct-ConhostArea-Server labels 2026-01-31 00:49:50 +00:00
claunia commented 2026-01-31 00:49:51 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 19, 2020):

I don't believe there is an equivalent. Perhaps there should be!
I'm tagging this one up as a feature request for the console host. Our bar for features there is pretty high (since getting APIs through API review can take some time), but it's still worth tracking them

@DHowett-MSFT commented on GitHub (Mar 19, 2020): I don't believe there is an equivalent. Perhaps there should be! I'm tagging this one up as a feature request for the console host. Our bar for features there is pretty high (since getting APIs through API review can take some time), but it's still worth tracking them
claunia commented 2026-01-31 00:49:51 +00:00
Author
Owner
Copy Link

@eryksun commented on GitHub (Mar 21, 2020):

This is quite convenient for certain types of applications since it means you won't get unexpected data back from reading stdin after you've made changes to terminal settings.

Doesn't FlushConsoleInputBuffer suffice for this?

@eryksun commented on GitHub (Mar 21, 2020): > This is quite convenient for certain types of applications since it means you won't get unexpected data back from reading stdin after you've made changes to terminal settings. Doesn't [`FlushConsoleInputBuffer`](https://docs.microsoft.com/en-us/windows/console/flushconsoleinputbuffer) suffice for this?
claunia commented 2026-01-31 00:49:51 +00:00
Author
Owner
Copy Link

@alexrp commented on GitHub (Mar 21, 2020):

Oh, I think that'll actually suffice for my case, yes.

Strictly speaking, I believe SetConsoleMode() + FlushConsoleInputBuffer() doesn't have exactly the same semantics as tcsetattr(..., TCSAFLUSH, ...). AFAIK the latter is supposed to be a single atomic operation. Off the top of my head, though, I can't think of any situations where the difference would matter.

@alexrp commented on GitHub (Mar 21, 2020): Oh, I think that'll actually suffice for my case, yes. Strictly speaking, I believe `SetConsoleMode()` + `FlushConsoleInputBuffer()` doesn't have exactly the same semantics as `tcsetattr(..., TCSAFLUSH, ...)`. AFAIK the latter is supposed to be a single atomic operation. Off the top of my head, though, I can't think of any situations where the difference would matter.
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-Server Issue-Feature Product-Conhost
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#6892
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?