Fix extra carriage returns in piped ANSI output on Windows #3442
+19
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes incorrect line endings in ANSI-colored output when redirected or piped on Windows terminals. A possible fix for #3138.
Problem
When using
fwrite()
on Windows, the CRT applies text-mode translation, converting\n
to\r\n
. This results in an extra carriage return (\r
) being injected, especially noticeable when ANSI-colored output is redirected or piped.Solution
On Windows, replace
fwrite()
with a direct call toWriteFile()
using the native file handle obtained from_get_osfhandle(_fileno(...))
. This bypasses the CRT entirely, ensuring output is written exactly as intended, without automatic newline translation.Code Change
CMake
Also included ansicolor_sink-inl.h explicitly in the build to avoid linking issues (when linking to static library).