Small "unwrapping" quirk #7173

Closed
opened 2026-01-31 00:57:02 +00:00 by claunia · 4 comments
Owner

Originally created by @nurbles on GitHub (Mar 27, 2020).

Environment

Windows build number: [Version 10.0.18363.720]
Windows Terminal version (if applicable): 0.10.7810

Any other software? no

Steps to reproduce

I was using a CMD shell for a directory listing. Some names (I used dir *.c /s/b) were longer than the window's width and were wrapped. When I dragged the right side of the window, I was pleasantly surprised to see the long lines "unwrap" ... at least until a couple of them somehow 'grabbed' the next line from the screen and appended it to themselves. I cannot see a way to attach a screen shot, so you can see it on my web site bad unwrap example

If you want to use the exact set of files I was using, get calibre-master from github, extract the files and issue the same command I used (shown above and in the screen shot) with the window only about 60-70 characters wide. Unfortunately, it doesn't always occur, but I got it to happen 3 out of 5 times, with different numbers of joined lines each time.

Expected behavior

I expected each separate line of output to remain separate.

Actual behavior

When the output is "unwrapped" as the window gets wider, some lines mysteriously join with the next (or previous?) line of output to make an even longer line that is still wrapped!

Originally created by @nurbles on GitHub (Mar 27, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Version 10.0.18363.720] Windows Terminal version (if applicable): 0.10.7810 Any other software? no ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> I was using a CMD shell for a directory listing. Some names (I used `dir *.c /s/b`) were longer than the window's width and were wrapped. When I dragged the right side of the window, I was pleasantly surprised to see the long lines "unwrap" ... at least until a couple of them somehow 'grabbed' the next line from the screen and appended it to themselves. I cannot see a way to attach a screen shot, so you can see it on my web site [bad unwrap example](https://www.svalli.com/files/badwrap.png) If you want to use the _exact_ set of files I was using, get [calibre-master from github](https://github.com/kovidgoyal/calibre), extract the files and issue the same command I used (shown above and in the screen shot) with the window only about 60-70 characters wide. Unfortunately, it doesn't always occur, but I got it to happen 3 out of 5 times, with different numbers of joined lines each time. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I expected each separate line of output to remain **separate**. # Actual behavior <!-- What's actually happening? --> When the output is "unwrapped" as the window gets wider, some lines mysteriously join with the next (or previous?) line of output to make an even **longer** line that is still wrapped!
claunia added the Product-ConhostResolution-Duplicate labels 2026-01-31 00:57:02 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Mar 27, 2020):

Okay this is the "you print a line that's exactly the width of the terminal, and we can't tell that the line actually broke there". It might be #3088, but I'm not positive

@zadjii-msft commented on GitHub (Mar 27, 2020): Okay this is the "you print a line that's exactly the width of the terminal, and we can't tell that the line actually broke there". It _might_ be #3088, but I'm not positive
Author
Owner

@nurbles commented on GitHub (Mar 30, 2020):

Yes, I think this is the same thing. Sorry for the duplicate report, but I would NEVER have EVER found it searching for size/wrap issues as I was doing. Feel free to close this and I will got vote for the referenced issue instead.

@nurbles commented on GitHub (Mar 30, 2020): Yes, I think this is the same thing. Sorry for the duplicate report, but I would **NEVER** have **EVER** found it searching for size/wrap issues as I was doing. Feel free to close this and I will got vote for the referenced issue instead.
Author
Owner

@zadjii-msft commented on GitHub (Mar 30, 2020):

Haha I wouldn't blame you, that's probably only apparent to someone who's been spending his last 3 months working on nothing but resizing. Thanks for following up!

/dup #3088

@zadjii-msft commented on GitHub (Mar 30, 2020): Haha I wouldn't blame you, that's probably only apparent to someone who's been spending his last 3 months working on [nothing but resizing](https://github.com/microsoft/terminal/issues/4200). Thanks for following up! /dup #3088
Author
Owner

@ghost commented on GitHub (Mar 30, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Mar 30, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7173