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

Fails to launch maximized/fullscreen and the given profile #10199

New Issue
Closed
opened 2026-01-31 02:15:06 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:15:06 +00:00
Owner
Copy Link

Originally created by @Guiorgy on GitHub (Aug 17, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.1016]
Windows Terminal version (if applicable): Version: 1.1.2233.0

Steps to reproduce

Open CMD and start wt maximized/fullscreen and a given profile, e.i. wt -M -p "Command Prompt"

Expected behavior

Windows Terminal opens in maximized mode with the "Command Prompt" profile

Actual behavior

Doesn't start and gives error:
image

Additional information

  • wt -M
    launches the terminal in maximized mode with default profile
  • wt -p "Command Prompt" -d D:/ ; -M
    launches the terminal maximized and the given profile, but with a second tab with the default profile
  • wt -p "Command Prompt" -d D:/ ; -M split-pane -d D:/ -p "Windows PowerShell"
    launches the terminal with 2 tabs with the selected profiles in maximized mode
  • wt -M -p "Command Prompt" -d D:/ ; split-pane -d D:/ -p "Windows PowerShell"
    doesn't work
Originally created by @Guiorgy on GitHub (Aug 17, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.1016] Windows Terminal version (if applicable): Version: 1.1.2233.0 ``` # Steps to reproduce Open **CMD** and start wt maximized/fullscreen and a given profile, e.i. `wt -M -p "Command Prompt"` # Expected behavior Windows Terminal opens in maximized mode with the "Command Prompt" profile # Actual behavior Doesn't start and gives error: ![image](https://user-images.githubusercontent.com/27736965/90419071-1265da00-e0c7-11ea-9465-557f1d55a2ab.png) # Additional information - `wt -M` launches the terminal in maximized mode with default profile - `wt -p "Command Prompt" -d D:/ ; -M` launches the terminal maximized and the given profile, but with a second tab with the default profile - `wt -p "Command Prompt" -d D:/ ; -M split-pane -d D:/ -p "Windows PowerShell"` launches the terminal with 2 tabs with the selected profiles in maximized mode - `wt -M -p "Command Prompt" -d D:/ ; split-pane -d D:/ -p "Windows PowerShell"` doesn't work
claunia commented 2026-01-31 02:15:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 17, 2020):

-M and -F are only available in version 1.2+.

@DHowett commented on GitHub (Aug 17, 2020): `-M` and `-F` are only available in version 1.2+.
claunia commented 2026-01-31 02:15:08 +00:00
Author
Owner
Copy Link

@Guiorgy commented on GitHub (Aug 17, 2020):

@DHowett
The docs didn't mention a version restriction. But more importantly, as I mentioned at the end of my post, wt -M as well as wt -p "profile 1" ; -M split-pane -p "profile 2" do work with my version of the terminal, so saying that -M/-F are only available in 1.2 can't be right?

@Guiorgy commented on GitHub (Aug 17, 2020): @DHowett The [docs](https://docs.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows) didn't mention a version restriction. But more importantly, as I mentioned at the end of my post, `wt -M` as well as `wt -p "profile 1" ; -M split-pane -p "profile 2"` do work with my version of the terminal, so saying that `-M/-F` are *only* available in *1.2* can't be right?
claunia commented 2026-01-31 02:15:09 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 17, 2020):

Whoops, you're totally right. This is an unusual interaction between the "default" command (new-tab) and arguments that belong to wt.

Right now, wt is treated like wt new-tab. Unfortunately, this means that wt -M is treated like wt new-tab -M, which definitely isn't valid. -M is an argument for the global context (and can only be specified before a command).

Workaround:

wt -M new-tab -p "Command prompt"

That also explains why your -M split-pane example works.

Sorry about that!

/cc @zadjii-msft

@DHowett commented on GitHub (Aug 17, 2020): Whoops, you're totally right. This is an unusual interaction between the "default" command (`new-tab`) and arguments that belong to `wt`. Right now, `wt` is treated like `wt new-tab`. Unfortunately, this means that `wt -M` is treated like `wt new-tab -M`, which definitely isn't valid. `-M` is an argument for the global context (and can only be specified before a command). Workaround: ``` wt -M new-tab -p "Command prompt" ``` That also explains why your `-M split-pane` example works. Sorry about that! /cc @zadjii-msft
claunia commented 2026-01-31 02:15:09 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 28, 2021):

:tada:This issue was addressed in #8315, which has now been successfully released as Windows Terminal v1.5.10271.0.🎉

Handy links:

@ghost commented on GitHub (Jan 28, 2021): :tada:This issue was addressed in #8315, which has now been successfully released as `Windows Terminal v1.5.10271.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.5.10271.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 02:15:09 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 28, 2021):

:tada:This issue was addressed in #8315, which has now been successfully released as Windows Terminal Preview v1.6.10272.0.🎉

Handy links:

@ghost commented on GitHub (Jan 28, 2021): :tada:This issue was addressed in #8315, which has now been successfully released as `Windows Terminal Preview v1.6.10272.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.6.10272.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-Commandline Issue-Bug Needs-Tag-Fix Priority-2 Product-Terminal Resolution-Fix-Committed
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#10199
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?