starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 16:34:42 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Bash on Ubuntu on Windows drawing issues while resizing window #22

New Issue
Closed
opened 2026-01-30 21:39:54 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 21:39:54 +00:00
Owner
Copy Link

Originally created by @SilviuArdelean on GitHub (Sep 12, 2017).

Updating a Raspberry Pi with Raspbian OS using 'apt' via SSH in Bash for Windows and resizing the window during the upgrade phase (sudo apt upgrade -y) seems to have rows drawing issues.

I was able to reproduce it also within my Bash sub-system while upgrading it.

clipboard01_bash_resize_while_updating_apt
clipboard02_bash_resize_while_upgrading_apt
clipboard03_bash_resize_while_upgrading_apt
clipboard04_bash_resize_while_upgrading_apt

Originally created by @SilviuArdelean on GitHub (Sep 12, 2017). Updating a Raspberry Pi with Raspbian OS using 'apt' via SSH in Bash for Windows and resizing the window during the upgrade phase (_sudo apt upgrade -y_) seems to have rows drawing issues. I was able to reproduce it also within my Bash sub-system while upgrading it. ![clipboard01_bash_resize_while_updating_apt](https://user-images.githubusercontent.com/5840603/30311426-d78cb180-979d-11e7-96b3-57117365243d.jpg) ![clipboard02_bash_resize_while_upgrading_apt](https://user-images.githubusercontent.com/5840603/30311429-d792f48c-979d-11e7-9bf2-585eb03bff1f.jpg) ![clipboard03_bash_resize_while_upgrading_apt](https://user-images.githubusercontent.com/5840603/30311427-d79131ec-979d-11e7-81bb-c8924b365ef0.jpg) ![clipboard04_bash_resize_while_upgrading_apt](https://user-images.githubusercontent.com/5840603/30311428-d792c624-979d-11e7-8181-000ed99fffba.jpg)
claunia added the Issue-FeatureProduct-ConhostArea-OutputNeeds-Triage labels 2026-01-30 21:39:54 +00:00
claunia commented 2026-01-30 21:39:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 13, 2017):

I can confirm that this is in fact happening. I can understand why it's happening, given the current workings of the console. However, I don't think a fix would be super easy. I believe this has something to do with the Console reflowing the text after a resize event. We keep redrawing the buffer every time the size changes, and then apt is also redrawing on top of that, and everyone gets confused. We might be able to defer reflowing until the resize has stopped, but that might not resolve the problem entirely, and might make it worse.

I'll add it to my bug backlog either way.

@zadjii-msft commented on GitHub (Sep 13, 2017): I can confirm that this is in fact happening. I can understand why it's happening, given the current workings of the console. However, I don't think a fix would be super easy. I believe this has something to do with the Console reflowing the text after a resize event. We keep redrawing the buffer every time the size changes, and then apt is also redrawing on top of that, and everyone gets confused. We might be able to defer reflowing until the resize has stopped, but that might not resolve the problem entirely, and might make it worse. I'll add it to my bug backlog either way.
claunia commented 2026-01-30 21:39:55 +00:00
Author
Owner
Copy Link

@noscript commented on GitHub (Nov 14, 2017):

The problem has probably something do with recognizing \r or ^H.

@noscript commented on GitHub (Nov 14, 2017): The problem has probably something do with recognizing `\r` or `^H`.
claunia commented 2026-01-30 21:39:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 28, 2017):

So, I've taken a closer look at this. I believe the "Right Way" to fix this is to implement a more unix-y buffer. Unfortunately that's a little bit bigger of a task then we can get done for the next release, but (without committing to anything) we do have work planned in that area.

In the meantime, I'm replacing the "bug" label with the "feature" label - still on our radar, just a little bit farther out.

@zadjii-msft commented on GitHub (Nov 28, 2017): So, I've taken a closer look at this. I believe the "Right Way" to fix this is to implement a more unix-y buffer. Unfortunately that's a little bit bigger of a task then we can get done for the next release, but (without committing to anything) we do have work planned in that area. In the meantime, I'm replacing the "bug" label with the "feature" label - still on our radar, just a little bit farther out.
claunia commented 2026-01-30 21:39:55 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 10, 2024):

Yeah, now that #8000 is done, we think that this is as good as it gets. Closing.

@carlos-zamora commented on GitHub (Jul 10, 2024): Yeah, now that #8000 is done, we think that this is as good as it gets. Closing.
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-Feature Needs-Triage Product-Conhost
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#22
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?