Resize when git diff's ^M exist expands background #7013

Closed
opened 2026-01-31 00:52:54 +00:00 by claunia · 2 comments
Owner

Originally created by @carlos-zamora on GitHub (Mar 19, 2020).

Environment

Windows build number: 10.0.19588.0
Windows Terminal version (if applicable):0.10.781.0

Steps to reproduce

  1. Maximize terminal (I have it on a portrait monitor)
  2. open pane right under it
  3. on top terminal, git diff with some actual output
  4. resize pane down past the halfway mark

Expected behavior

Just a normal resize, nothing special.

Actual behavior

git diff resize

Other notes

I tried repro-ing when the terminal is not maximized. That didn't work, funny enough.

As you can see in the gif, it seems to not happen until you hit the halfway point.

Originally created by @carlos-zamora on GitHub (Mar 19, 2020). # Environment ```none Windows build number: 10.0.19588.0 Windows Terminal version (if applicable):0.10.781.0 ``` # Steps to reproduce 1. Maximize terminal (I have it on a portrait monitor) 2. open pane right under it 3. on top terminal, `git diff` with some actual output 4. resize pane down past the halfway mark # Expected behavior Just a normal resize, nothing special. # Actual behavior ![git diff resize](https://user-images.githubusercontent.com/11050425/77123752-45178380-69fe-11ea-9e90-4bfef2a4dc94.gif) # Other notes I tried repro-ing when the terminal is not maximized. That didn't work, funny enough. As you can see in the gif, it seems to not happen until you hit the halfway point.
claunia added the Issue-BugResolution-DuplicateProduct-Terminal labels 2026-01-31 00:52:54 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Mar 19, 2020):

/dup #32

@DHowett-MSFT commented on GitHub (Mar 19, 2020): /dup #32
Author
Owner

@ghost commented on GitHub (Mar 19, 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 19, 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#7013