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

Windows terminal does not work the same as ConHost when using C# Console methods #1969

New Issue
Closed
opened 2026-01-30 22:43:07 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:43:07 +00:00
Owner
Copy Link

Originally created by @teobugslayer on GitHub (Jun 23, 2019).

I am using this code (C#, .Net core 3 preview 7). Some imports and constants omitted for brevity.
There is several inconsistencies between ConHost and Windows Terminal (WT):

  1. Using this code:
Console.SetWindowSize(maxX, maxY); // using constants 132 and 43 here
Console.SetBufferSize(maxX, maxY);
SetConsoleMode(hOut, dwMode | ENABLE_VIRTUAL_TERMINAL_PROCESSING); // DllImport'ed
  • In WT there's a vertical scroll bar and I can scroll. This is contrary to what I want
  1. Using this code:
Console.Clear();
ConsoleWrite(/*a string with length the entire screen buffer*/)
  • Sometimes the text disappears. Once I got into this state I (as a human using the console) got very confused because if I scroll up or down, the text re-appears. It's kind of hard to put into words but the behavior is crazy funny when seen in person
  1. Using this code
Console.CursorVisible = false;

does not work. I can see a blinking cursor.

Environment

Windows build number: Version 10.0.18362.175
Windows Terminal version (if applicable): 0.2.1715.0

Any other software?

Steps to reproduce

Expected behavior

When using methods of the standard .net core System.Console class, they should work as documented. Also, WT and ConHost should have the same behavor (unless ConHost is wrong)

Actual behavior

See bug description.

Originally created by @teobugslayer on GitHub (Jun 23, 2019). I am using this code (C#, .Net core 3 preview 7). Some imports and constants omitted for brevity. There is several inconsistencies between ConHost and Windows Terminal (WT): 1. Using this code: ```C# Console.SetWindowSize(maxX, maxY); // using constants 132 and 43 here Console.SetBufferSize(maxX, maxY); SetConsoleMode(hOut, dwMode | ENABLE_VIRTUAL_TERMINAL_PROCESSING); // DllImport'ed ``` * In WT there's a vertical scroll bar and I can scroll. This is contrary to what I want 2. Using this code: ```C# Console.Clear(); ConsoleWrite(/*a string with length the entire screen buffer*/) ``` * Sometimes the text disappears. Once I got into this state I (as a human using the console) got very confused because if I scroll up or down, the text re-appears. It's kind of hard to put into words but the behavior is crazy funny when seen in person 3. Using this code ```C# Console.CursorVisible = false; ``` does not work. I can see a blinking cursor. # Environment ```none Windows build number: Version 10.0.18362.175 Windows Terminal version (if applicable): 0.2.1715.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior When using methods of the standard .net core System.Console class, they should work as documented. Also, WT and ConHost should have the same behavor (unless ConHost is wrong) # Actual behavior See bug description.
claunia added the Issue-QuestionResolution-By-DesignArea-OutputProduct-Conpty labels 2026-01-30 22:43:07 +00:00
claunia commented 2026-01-30 22:43:08 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

Specifically, it doesn't work the same for the methods that set the screen and buffer size. There's a little complication here -- Windows Terminal's scrollback buffer is completely separate from Conhost's, and it's very difficult to fit terminals into the Windows Console model where an application gets full control over its scrollback...

This leads to some visual artifacting when applications try to do stuff like this.

@DHowett-MSFT commented on GitHub (Jun 24, 2019): **Specifically**, it doesn't work the same for the methods that set the screen and buffer size. There's a little complication here -- Windows Terminal's scrollback buffer is completely separate from Conhost's, and it's very difficult to fit terminals into the Windows Console model where an application gets full control over its scrollback... This leads to some visual artifacting when applications try to do stuff like this.
claunia commented 2026-01-30 22:43:08 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

(Cursor visibility is #1127)

@DHowett-MSFT commented on GitHub (Jun 24, 2019): (Cursor visibility is #1127)
claunia commented 2026-01-30 22:43:09 +00:00
Author
Owner
Copy Link

@teobugslayer commented on GitHub (Jun 26, 2019):

Hi @dhowett-msft,

Thank you for the explanation. The code i mentioned exists to avoid visual artefacts on conhost. I'd be grateful to get guidance what would be the correct approach for WT and how can i programmatically distinguish between the two.

I am willing to work within the rules of the system, but i do not know what the rules are.

@teobugslayer commented on GitHub (Jun 26, 2019): Hi @dhowett-msft, Thank you for the explanation. The code i mentioned exists to avoid visual artefacts on conhost. I'd be grateful to get guidance what would be the correct approach for WT and how can i programmatically distinguish between the two. I am willing to work within the rules of the system, but i do not know what the rules are.
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-Output Issue-Question Product-Conpty 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#1969
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?