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

A windowing mode that allows the Terminal to grow in size as text is output #17273

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

Originally created by @zadjii-msft on GitHub (Apr 18, 2022).

The latest from the "I just had a four hour roadtrip so I was brainstorming idly" foundry of showerthougts

What if there was a way to indicate that we wanted the control to start at 1 line tall, and resize as text was output, till it reached initialRows (at which point it would start scrolling). This I think was offhand mentioned by a PM as like, a powertoys run-like UI, and I finally wrapped my head around the idea.

We'd either need to:

  • inform the Terminal that it's actual viewport size is initialRowsxinitialCols, and that it's in this virtual size mode, and it should grow in size to the initialSize. SCREEN_INFO already does something weird with virtualBottom, this might end up being similar. The Terminal layer would just keep reporting new buffer sizes until it hit the originally requested size.
  • Allow the TermControl to fake this out on it's own as it's scrolling? So like, when the Terminal says that the scroll position changed, TermControl says "mhm sure" and actually just increases it's own height. This implementation was less brainstormed so might not work as well.
  • The App layer needs to be able to listen to the size of the TermControl and resize the window to allow it to fit

I'm imagining you combine this with center on launch and with Focus Mode, and a global hotkey, now you've got a PowerToys Run-like box that appears in the center of the monitor, you run some command, and then you {do something to dismiss it. closeOnFocusLost?}

Refer also to:

  • #5094
    • Much more discussion here of "what do we do if a cmdline app wants a resize?". This is similar in the regards that " has asked the TermControl to be a different size, how should the App & Window respond to that"?
  • #10660
    • But more aggressive. Close on focus lost.
  • #9992
    • For the sense of a globalSummon action to run wt -w _run that's got {focus mode, launch centered, default profile, <this setting>} all enabled.
Originally created by @zadjii-msft on GitHub (Apr 18, 2022). _The latest from the "I just had a four hour roadtrip so I was brainstorming idly" foundry of showerthougts_ What if there was a way to indicate that we wanted the control to start at 1 line tall, and resize as text was output, till it reached `initialRows` (at which point it would start scrolling). This I think was offhand mentioned by a PM as like, a powertoys run-like UI, and I finally wrapped my head around the idea. We'd either need to: * inform the `Terminal` that it's actual viewport size is `initialRows`x`initialCols`, and that it's in this virtual size mode, and it should grow in size to the `initialSize`. `SCREEN_INFO` already does something weird with `virtualBottom`, this might end up being similar. The `Terminal` layer would just keep reporting new buffer sizes until it hit the originally requested size. * Allow the `TermControl` to fake this out on it's own as it's scrolling? So like, when the `Terminal` says that the scroll position changed, `TermControl` says "mhm sure" and actually just increases it's own height. This implementation was less brainstormed so might not work as well. * The App layer needs to be able to listen to the size of the TermControl and resize the window to allow it to fit I'm imagining you combine this with center on launch and with Focus Mode, and a global hotkey, now you've got a PowerToys Run-like box that appears in the center of the monitor, you run some command, and then you {do something to dismiss it. `closeOnFocusLost`?} Refer also to: * #5094 * Much more discussion here of "what do we do if a cmdline app wants a resize?". This is similar in the regards that "<someone> has asked the `TermControl` to be a different size, how should the `App` & `Window` respond to that"? * #10660 * But more aggressive. Close on focus lost. * #9992 * For the sense of a `globalSummon` action to run `wt -w _run` that's got `{focus mode, launch centered, default profile, <this setting>}` all enabled.
claunia added the Issue-FeatureProduct-TerminalArea-TerminalControlArea-Windowing labels 2026-01-31 05:37:29 +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 Area-TerminalControl Area-Windowing Issue-Feature Product-Terminal
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#17273
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?