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

Command line "-F" (fullscreen) should work in an already running instance #22284

New Issue
Open
opened 2026-01-31 08:08:51 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:08:51 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Sep 12, 2024).

WindowsTerminal 1.21.2408.23001

In an already-running WT, this command splits the current pane and focuses the old one.

wt sp -p TCC33 -V ; move-focus left

This command does the same thing, not making it fullscreen.

wt -F sp -p TCC33 -V ; move-focus left

Is that as expected?

Originally created by @vefatica on GitHub (Sep 12, 2024). WindowsTerminal 1.21.2408.23001 In an already-running WT, this command splits the current pane and focuses the old one. `wt sp -p TCC33 -V ; move-focus left` This command does the same thing, not making it fullscreen. `wt -F sp -p TCC33 -V ; move-focus left` Is that as expected?
claunia added the Issue-FeatureProduct-TerminalArea-Remoting labels 2026-01-31 08:08:51 +00:00
claunia commented 2026-01-31 08:08:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 14, 2024):

With the setup you've got, that's what I'd expect. -F only affects the creation of new windows. Since your settings are such that new instances of wt open in the current window by default, the second commandline you provided will get sent to the current window, and not make a new one.

I could have swore there was an issue around here for "a CLI flag to toggle the fullscreen state of the window". but I can't find it currently

@zadjii-msft commented on GitHub (Sep 14, 2024): With the setup you've got, that's what I'd expect. `-F` only affects the creation of new windows. Since your settings are such that new instances of `wt` open in the current window by default, the second commandline you provided will get sent to the current window, and not make a new one. I could have swore there was an issue around here for "a CLI flag to toggle the fullscreen state of the window". but I can't find it currently
claunia commented 2026-01-31 08:08:52 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 14, 2024):

I don't understand the "setup" part.

-F only affects the creation of new windows

Is that the bottom line?

@vefatica commented on GitHub (Sep 14, 2024): I don't understand the "setup" part. > -F only affects the creation of new windows Is that the bottom line?
claunia commented 2026-01-31 08:08:52 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 16, 2024):

I suppose the question is whether -F should full-screen the window even if it already existed, right? (I personally think it would make sense.)

@lhecker commented on GitHub (Sep 16, 2024): I suppose the question is whether `-F` should full-screen the window even if it already existed, right? (I personally think it would make sense.)
claunia commented 2026-01-31 08:08:53 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 16, 2024):

Looking at the "wt /?" message box, it seems that the "options" do not affect an already existing window while the "subcommands" do (or can). No doubt there's a distinction between the ways the two are handled. I wanted -F to affect the current window. I could simulate F11 but that would require WT to have input focus.

Is there a message that can be sent to the Cascadia window that will cause it to go fullscreen?

@vefatica commented on GitHub (Sep 16, 2024): Looking at the "wt /?" message box, it seems that the "options" do not affect an already existing window while the "subcommands" do (or can). No doubt there's a distinction between the ways the two are handled. I wanted -F to affect the current window. I could simulate F11 but that would require WT to have input focus. Is there a message that can be sent to the Cascadia window that will cause it to go fullscreen?
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-Remoting 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#22284
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?