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

Terminal doesn't resize if historySize is set to ~32700 or larger #5027

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

Originally created by @sphennings on GitHub (Nov 15, 2019).

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version: 0.6.2951.0

Steps to reproduce

  1. Set the historySize of a terminal profile to a sufficiently large number. (I modified the default profiles in my testing)
  • 32747 or larger for powershell
  • 32797 or larger for wsl
  1. Create a new terminal tab using the modified profile
  2. Record the current reported terminal size
  • Use $Host.UI.RawUI.WindowSize.Width; $Host.UI.RawUI.WindowSize.Height for powershell
  • Use tput cols; tput lines for wsl
  1. Resize the terminal window
  2. Record the new reported terminal size

Expected behavior

Resizing the terminal window should change the reported terminal dimensions.

Terminal resize behavior should be unaffected by historySize.

Actual behavior

When the historySize profile setting is sufficiently large resizing the terminal window does not change the reported terminal dimensions.

Originally created by @sphennings on GitHub (Nov 15, 2019). # Environment ``` Windows build number: Microsoft Windows NT 10.0.18362.0 Windows Terminal version: 0.6.2951.0 ``` # Steps to reproduce 1. Set the `historySize` of a terminal profile to a sufficiently large number. (I modified the default profiles in my testing) - 32747 or larger for powershell - 32797 or larger for wsl 2. Create a new terminal tab using the modified profile 3. Record the current reported terminal size - Use `$Host.UI.RawUI.WindowSize.Width; $Host.UI.RawUI.WindowSize.Height` for powershell - Use `tput cols; tput lines` for wsl 4. Resize the terminal window 5. Record the new reported terminal size # Expected behavior Resizing the terminal window should change the reported terminal dimensions. Terminal resize behavior should be unaffected by historySize. # Actual behavior When the historySize profile setting is sufficiently large resizing the terminal window does not change the reported terminal dimensions.
claunia added the Resolution-Duplicate label 2026-01-31 00:03:20 +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#5027
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?