starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Powershell 6 resizing issues #5757

New Issue
Open
opened 2026-01-31 00:20:55 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:20:55 +00:00
Owner
Copy Link

Originally created by @sbenalohm on GitHub (Jan 2, 2020).

Environment

Windows build number: Microsoft Windows 10.0.18363
Windows Terminal version (if applicable): 0.7.3451.0

Any other software?
PowerShell Core 6.2.3

Steps to reproduce

Run PowerShell Core 6.2.3 in Windows Terminal, resize the window in any manner.

Expected behavior

The terminal prompt and existing printed text will be resized (i.e. line wrapping) and realigned to put the active prompt at the bottom of the window or at the lowest line if there aren't enough history lines to fill up the window.

All profiles other than PS6 (WSL, CMD, original PowerShell, Azure Cloud Terminal) are working fine in this regard, as well as the default PS6 terminal (not running it in Windows Terminal).

Actual behavior

The text stays in the same place relative to the border dimensions that the terminal/tab was instantiated with.

When the window is enlarged, all visible text remains inside the smaller original borders. See that in the 2nd image the output of the top command is cut off even though there is empty space below the last prompt line. Prompt lines will never fill this empty space.
InitialSizeFull
FirstResizeCutsOutput

If a new tab is opened once the window is larger, these new dimensions are accurately rendered with the new terminal tab. See how there is now no empty space below the last prompt.
FirstResizeNewTabMoreOutputNoScrollbar

When the window is made smaller, the printed text remains in the larger original borders making the current line (the cursor/new text) not visible as it remains outside the new smaller bounds. In the first image below I've typed a bogus command into the prompt, but it is not visible as it is a few lines below the bottom of the resized window. After hitting enter a few times, the 2nd image shows that the command ran, but was not visible in the terminal until enough new lines pushed it up into the view of the resized window.
SecondResizeUndersizePromptNotVisible
SecondResizeUndersizePromptNotVisibleStartOutput

Originally created by @sbenalohm on GitHub (Jan 2, 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: Microsoft Windows 10.0.18363 Windows Terminal version (if applicable): 0.7.3451.0 Any other software? PowerShell Core 6.2.3 ``` # Steps to reproduce Run PowerShell Core 6.2.3 in Windows Terminal, resize the window in any manner. # Expected behavior The terminal prompt and existing printed text will be resized (i.e. line wrapping) and realigned to put the active prompt at the bottom of the window or at the lowest line if there aren't enough history lines to fill up the window. All profiles other than PS6 (WSL, CMD, original PowerShell, Azure Cloud Terminal) are working fine in this regard, as well as the default PS6 terminal (not running it in Windows Terminal). # Actual behavior The text stays in the same place relative to the border dimensions that the terminal/tab was instantiated with. When the window is enlarged, all visible text remains inside the smaller original borders. See that in the 2nd image the output of the top command is cut off even though there is empty space below the last prompt line. Prompt lines will never fill this empty space. ![InitialSizeFull](https://user-images.githubusercontent.com/47365418/71695689-bc2a6d80-2d67-11ea-8d0c-28e68eb3a5c8.jpg) ![FirstResizeCutsOutput](https://user-images.githubusercontent.com/47365418/71695693-bcc30400-2d67-11ea-83d0-96d1edc69aa9.jpg) If a new tab is opened once the window is larger, these new dimensions are accurately rendered with the new terminal tab. See how there is now no empty space below the last prompt. ![FirstResizeNewTabMoreOutputNoScrollbar](https://user-images.githubusercontent.com/47365418/71695688-bb91d700-2d67-11ea-995d-43b3a76e7e63.jpg) When the window is made smaller, the printed text remains in the larger original borders making the current line (the cursor/new text) not visible as it remains outside the new smaller bounds. In the first image below I've typed a bogus command into the prompt, but it is not visible as it is a few lines below the bottom of the resized window. After hitting enter a few times, the 2nd image shows that the command ran, but was not visible in the terminal until enough new lines pushed it up into the view of the resized window. ![SecondResizeUndersizePromptNotVisible](https://user-images.githubusercontent.com/47365418/71695690-bc2a6d80-2d67-11ea-98b0-18f53ea1c5c2.jpg) ![SecondResizeUndersizePromptNotVisibleStartOutput](https://user-images.githubusercontent.com/47365418/71695692-bcc30400-2d67-11ea-8410-e49747331d2d.jpg)
claunia added the Resolution-Duplicate label 2026-01-31 00:20:55 +00:00
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 Resolution-Duplicate
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#5757
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?