maximize inserts extra empty lines #21239

Closed
opened 2026-01-31 07:37:26 +00:00 by claunia · 6 comments
Owner

Originally created by @3052 on GitHub (Feb 12, 2024).

Windows Terminal version

terminal-1.19.10302.0

Windows build number

10.0.18363.0

Other Software

No response

Steps to reproduce

take this file:

https://github.com/microsoft/terminal/files/14251165/hello.txt

open terminal, and move it to half the screen with Windows+Left or Windows+Right. print file:

Get-Content hello.txt

notice because of the line width, the rows wrap around:

wrap

you might need to reduce window width further depending on monitor/font size. the above is expected, but I would assume that maximizing the window fixes the problem, it does not:

broken

Expected Behavior

No response

Actual Behavior

notice the random empty lines. note I also tested with:

terminal-1.20.10303.0

Originally created by @3052 on GitHub (Feb 12, 2024). ### Windows Terminal version terminal-1.19.10302.0 ### Windows build number 10.0.18363.0 ### Other Software _No response_ ### Steps to reproduce take this file: https://github.com/microsoft/terminal/files/14251165/hello.txt open terminal, and move it to half the screen with Windows+Left or Windows+Right. print file: ~~~ Get-Content hello.txt ~~~ notice because of the line width, the rows wrap around: > ![wrap](https://github.com/microsoft/terminal/assets/147215885/ef142ed1-a5f6-4e4c-b527-63f971557598) you might need to reduce window width further depending on monitor/font size. the above is expected, but I would assume that maximizing the window fixes the problem, it does not: > ![broken](https://github.com/microsoft/terminal/assets/147215885/4ae51f5c-324e-4878-a2f3-6f15cb0f4d7c) ### Expected Behavior _No response_ ### Actual Behavior notice the random empty lines. note I also tested with: terminal-1.20.10303.0
Author
Owner

@o-sdn-o commented on GitHub (Feb 13, 2024):

It appears that trailing whitespace characters carried to the next line during initial output are not considered printable characters and will not be returned to their line when the window is expanded.

image

image

@o-sdn-o commented on GitHub (Feb 13, 2024): It appears that trailing whitespace characters carried to the next line during initial output are not considered printable characters and will not be returned to their line when the window is expanded. ![image](https://github.com/microsoft/terminal/assets/11535558/d3f4aabc-9dc1-430b-be52-1e3bb725298d) ![image](https://github.com/microsoft/terminal/assets/11535558/63659e7f-c6f9-4b3c-b5c6-3a83ac41b8a4)
Author
Owner

@carlos-zamora commented on GitHub (Feb 14, 2024):

Thanks for the repro. We'll take a look at this.

@carlos-zamora commented on GitHub (Feb 14, 2024): Thanks for the repro. We'll take a look at this.
Author
Owner

@zadjii-msft commented on GitHub (Sep 4, 2024):

Is this fixed in Terminal 1.22/?

@zadjii-msft commented on GitHub (Sep 4, 2024): Is this fixed in Terminal 1.22/?
Author
Owner

@DHowett commented on GitHub (Sep 4, 2024):

It is available in the preview channel and on the releases page for this repository!

@DHowett commented on GitHub (Sep 4, 2024): It is available in the [preview channel](https://aka.ms/terminal-preview) and on the [releases page for this repository](https://github.com/microsoft/terminal/releases)!
Author
Owner

@3052 commented on GitHub (Sep 5, 2024):

yeah 1.22 seems to have fixed it - all other current versions including 1.21.2361 fail the test described in the original post

@3052 commented on GitHub (Sep 5, 2024): yeah 1.22 seems to have fixed it - all other current versions including 1.21.2361 fail the test described in the original post
Author
Owner

@lhecker commented on GitHub (Sep 5, 2024):

I'm glad to hear that 1.22 has fixed the issue. I don't think it'll be possible to backport the fixes to 1.21 unfortunately, because the fix was a large rewrite of our architecture.

I'll be closing this issue for now then. It'll be a few months until 1.22 becomes the next stable version.

@lhecker commented on GitHub (Sep 5, 2024): I'm glad to hear that 1.22 has fixed the issue. I don't think it'll be possible to backport the fixes to 1.21 unfortunately, because the fix was a large rewrite of our architecture. I'll be closing this issue for now then. It'll be a few months until 1.22 becomes the next stable version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21239