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

\n with ENABLE_PROCESSED_OUTPUT and without ENABLE_WRAP_AT_EOL_OUTPUT #23080

New Issue
Closed
opened 2026-01-31 08:31:43 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:31:43 +00:00
Owner
Copy Link

Originally created by @malxau-msft on GitHub (Mar 28, 2025).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.22.2362

Windows build number

10.0.19045

Other Software

No response

Steps to reproduce

Disable ENABLE_WRAP_AT_EOL_OUTPUT, keep ENABLE_PROCESSED_OUTPUT enabled, write to the end of line, then insert \n . Traditionally the newline would operate as CRLF (processed output semantics) and start at the beginning of the following line. Note this is Win32 semantics, VT semantics are different; in this sequence, VT support is not enabled.

In WT 1.22.x, this generates VT semantics. Replacing \n with \r\n works as expected.

#include <windows.h>

int main(int argc, char * argv[])
{
    CONSOLE_SCREEN_BUFFER_INFO screenBufferInfo;
    DWORD consoleWidth;
    DWORD charIndex;
    DWORD lineIndex;
    DWORD charsWritten;
    HANDLE consoleHandle;
    LPSTR buffer;

    consoleHandle = GetStdHandle(STD_OUTPUT_HANDLE);
    GetConsoleScreenBufferInfo(consoleHandle, &screenBufferInfo);
    consoleWidth = screenBufferInfo.dwSize.X;

    //
    //  Disable ENABLE_WRAP_AT_EOL_OUTPUT
    //
    SetConsoleMode(consoleHandle, ENABLE_PROCESSED_OUTPUT);
    buffer = malloc(consoleWidth + 1);

    for (lineIndex = 0; lineIndex < 3; lineIndex++) {
        for (charIndex = 0; charIndex < consoleWidth; charIndex++) {
            buffer[charIndex] = '1' + lineIndex;
        }
        WriteConsole(consoleHandle, buffer, consoleWidth, &charsWritten, NULL);
        WriteConsole(consoleHandle, "\n", 1, &charsWritten, NULL);
    }

    return 0;
}

Expected Behavior

Behavior in WT 1.21, as well as Conhost, including OpenConsole from WT 1.22:

Image

Actual Behavior

Behavior in WT 1.22:

Image

Originally created by @malxau-msft on GitHub (Mar 28, 2025). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.22.2362 ### Windows build number 10.0.19045 ### Other Software _No response_ ### Steps to reproduce Disable ENABLE_WRAP_AT_EOL_OUTPUT, keep ENABLE_PROCESSED_OUTPUT enabled, write to the end of line, then insert \n . Traditionally the newline would operate as CRLF (processed output semantics) and start at the beginning of the following line. Note this is Win32 semantics, VT semantics are different; in this sequence, VT support is not enabled. In WT 1.22.x, this generates VT semantics. Replacing \n with \r\n works as expected. ``` #include <windows.h> int main(int argc, char * argv[]) { CONSOLE_SCREEN_BUFFER_INFO screenBufferInfo; DWORD consoleWidth; DWORD charIndex; DWORD lineIndex; DWORD charsWritten; HANDLE consoleHandle; LPSTR buffer; consoleHandle = GetStdHandle(STD_OUTPUT_HANDLE); GetConsoleScreenBufferInfo(consoleHandle, &screenBufferInfo); consoleWidth = screenBufferInfo.dwSize.X; // // Disable ENABLE_WRAP_AT_EOL_OUTPUT // SetConsoleMode(consoleHandle, ENABLE_PROCESSED_OUTPUT); buffer = malloc(consoleWidth + 1); for (lineIndex = 0; lineIndex < 3; lineIndex++) { for (charIndex = 0; charIndex < consoleWidth; charIndex++) { buffer[charIndex] = '1' + lineIndex; } WriteConsole(consoleHandle, buffer, consoleWidth, &charsWritten, NULL); WriteConsole(consoleHandle, "\n", 1, &charsWritten, NULL); } return 0; } ``` ### Expected Behavior Behavior in WT 1.21, as well as Conhost, including OpenConsole from WT 1.22: ![Image](https://github.com/user-attachments/assets/77fcdf2e-5693-4294-965c-08c7f5e3a1f8) ### Actual Behavior Behavior in WT 1.22: ![Image](https://github.com/user-attachments/assets/296a4a57-0c42-4c7b-bd65-6c165e28eb35)
claunia added the Issue-BugNeeds-Tag-FixArea-ServerProduct-ConptyPriority-1 labels 2026-01-31 08:31:44 +00:00
claunia commented 2026-01-31 08:31:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 2, 2025):

Whoa, thanks for catching this! Probably an issue in the new (as of 1.22) translation layer for console APIs to VT. :)

@DHowett commented on GitHub (Apr 2, 2025): Whoa, thanks for catching this! Probably an issue in the new (as of 1.22) translation layer for console APIs to VT. :)
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-Bug Needs-Tag-Fix Priority-1 Product-Conpty
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#23080
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?