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

Terminal won't open maxmized when "Run" field in shortcut set to Maximized #3340

New Issue
Closed
opened 2026-01-30 23:19:04 +00:00 by claunia · 9 comments
claunia commented 2026-01-30 23:19:04 +00:00
Owner
Copy Link

Originally created by @miklevin on GitHub (Aug 10, 2019).

Environment

Windows build number: 10.0.18956.1000

Windows Terminal version (if applicable): 0.3.2142.0

Steps to reproduce

Drag tile from Windows Start Menu to desktop to create Link shortcut. Right-click shortcut icon and select properties. Change Run field to Maxmimized. Hit Apply. Close properties. Double-click shortcut icon. Terminal window does not open maxmimized, or at least it doesn't move the window to the upper-left of the screen the same way it would if you hit the Maxmimize button or Windows Key + up-arrow.

Expected behavior

Terminal window should open Maxmimized in the upper-left of the Screen appearing full-screen for immediate use the same way it would as if you hit the Maximize button on the Terminal window or pressed Windows Key + up-arrow.

Actual behavior

Terminal window is opening, but is positioned offset to the lower-right from what is expected. This requires an extra keystroke or mouse movement to maximize the window properly, which is a real show-stopper for terminal dandies like myself who thing you should be able to hit your keyboard shortcut to launch your Terminal and then immediately start using it.

Mike-Levin-Desktop-Shortcuts
Mike-Levin-Bash-Terminal

Originally created by @miklevin on GitHub (Aug 10, 2019). # Environment ```none Windows build number: 10.0.18956.1000 Windows Terminal version (if applicable): 0.3.2142.0 ``` # Steps to reproduce Drag tile from Windows Start Menu to desktop to create Link shortcut. Right-click shortcut icon and select properties. Change Run field to Maxmimized. Hit Apply. Close properties. Double-click shortcut icon. Terminal window does not open maxmimized, or at least it doesn't move the window to the upper-left of the screen the same way it would if you hit the Maxmimize button or Windows Key + up-arrow. # Expected behavior Terminal window should open Maxmimized in the upper-left of the Screen appearing full-screen for immediate use the same way it would as if you hit the Maximize button on the Terminal window or pressed Windows Key + up-arrow. # Actual behavior Terminal window is opening, but is positioned offset to the lower-right from what is expected. This requires an extra keystroke or mouse movement to maximize the window properly, which is a real show-stopper for terminal dandies like myself who thing you should be able to hit your keyboard shortcut to launch your Terminal and then immediately start using it. ![Mike-Levin-Desktop-Shortcuts](https://user-images.githubusercontent.com/4175278/62822331-ab2a5700-bb4f-11e9-9b5b-53959cb131aa.PNG) ![Mike-Levin-Bash-Terminal](https://user-images.githubusercontent.com/4175278/62822333-b087a180-bb4f-11e9-8c15-976603c0fe85.PNG)
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-30 23:19:04 +00:00
claunia commented 2026-01-30 23:19:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 13, 2019):

This is, unfortunately, a platform limitation. I have filed MSFT:23202140 on the appropriate team to see if we can't get something done about it.

@DHowett-MSFT commented on GitHub (Aug 13, 2019): This is, unfortunately, a platform limitation. I have filed MSFT:23202140 on the appropriate team to see if we can't get something done about it.
claunia commented 2026-01-30 23:19:05 +00:00
Author
Owner
Copy Link

@miklevin commented on GitHub (Aug 15, 2019):

In what way is that a platform limitation? It works on all other apps, just not here on Microsoft Terminal, like the key place where it should work. Not being able to pull up a full-screen with the OS's built-in keyboard shortcut system is a pretty big deal. Maybe further research is necessary before closing.

@miklevin commented on GitHub (Aug 15, 2019): In what way is that a platform limitation? It works on all other apps, just not here on Microsoft Terminal, like the key place where it should work. Not being able to pull up a full-screen with the OS's built-in keyboard shortcut system is a pretty big deal. Maybe further research is necessary before closing.
claunia commented 2026-01-30 23:19:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 15, 2019):

It's something that actually doesn't work for any Win32 packaged applications ("Centennial apps"). For example, with Edge or any WSL distro, that doesn't necessarily work. The flag that checkbox sets isn't getting properly passed to the STARTUPINFO of a centennial application.

@zadjii-msft commented on GitHub (Aug 15, 2019): It's something that actually doesn't work for any _Win32 packaged applications_ ("Centennial apps"). For example, with Edge or any WSL distro, that doesn't necessarily work. The flag that checkbox sets isn't getting properly passed to the `STARTUPINFO` of a centennial application.
claunia commented 2026-01-30 23:19:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 15, 2019):

Maybe further research is necessary

Here's a snippet of the bug I filed on the team that owns "centennial" activation:

It is possible to create a shortcut to a centennial application using "shell:appsfolder" It is further possible to configure that shortcut to spawn the application in Maximized/Minimized/Normal windowing mode.

image

The WinMain entrypoint has a parameter, "nShowCmd", which should receive this information.

I have created an application that displays a messagebox containing the value of nShowCmd. Here's an example when i run it in different circumstances.

  • UNPACKAGED (raw EXE)
    • Double-clicked in explorer
      • image
    • From a shortcut marked RUN MAXIMIZED
      • image
  • PACKAGED (Centennial)
    • Start Menu
      • image
    • shell:appsfolder
      • image
    • From a shortcut marked RUN MAXIMIZED
      • image

As you can see, the centennialized application never receives the show setting. This applies equally well to the App Execution alias.

Because of this, users who create shortcuts to traditional applications (including "Windows Terminal") distributed via centennialization will not be able to configure them to launch maximized.

This was reported by a member of the general public.

Would you like me to do more research?

@DHowett-MSFT commented on GitHub (Aug 15, 2019): > Maybe further research is necessary Here's a snippet of the bug I filed on the team that owns "centennial" activation: > It is possible to create a shortcut to a centennial application using "shell:appsfolder" It is further possible to configure that shortcut to spawn the application in Maximized/Minimized/Normal windowing mode. > > ![image](https://user-images.githubusercontent.com/14316954/63113969-86b3ed80-bf48-11e9-8870-e92393a16675.png) > > The WinMain entrypoint has a parameter, "nShowCmd", which should receive this information. > > I have created an application that displays a messagebox containing the value of nShowCmd. Here's an example when i run it in different circumstances. > > * UNPACKAGED (raw EXE) > * Double-clicked in explorer > * ![image](https://user-images.githubusercontent.com/14316954/63113983-8e739200-bf48-11e9-817f-0383fe1ac19a.png) > * From a shortcut marked RUN MAXIMIZED > * ![image](https://user-images.githubusercontent.com/14316954/63113997-95020980-bf48-11e9-8883-f0839ef0b1c3.png) > * PACKAGED (Centennial) > * Start Menu > * ![image](https://user-images.githubusercontent.com/14316954/63114004-99c6bd80-bf48-11e9-8050-ce5fcdf9ed59.png) > * shell:appsfolder > * ![image](https://user-images.githubusercontent.com/14316954/63114004-99c6bd80-bf48-11e9-8050-ce5fcdf9ed59.png) > * From a shortcut marked RUN MAXIMIZED > * ![image](https://user-images.githubusercontent.com/14316954/63114004-99c6bd80-bf48-11e9-8050-ce5fcdf9ed59.png) > > As you can see, the centennialized application never receives the show setting. This applies equally well to the App Execution alias. > > Because of this, users who create shortcuts to traditional applications (including "Windows Terminal") distributed via centennialization will not be able to configure them to launch maximized. > > This was reported by a member of the general public. Would you like me to do more research?
claunia commented 2026-01-30 23:19:06 +00:00
Author
Owner
Copy Link

@miklevin commented on GitHub (Aug 19, 2019):

Yes into a workaround. It's unreasonable for the main Microsoft Terminal app that's supposed to be a game changer and a big part of Microsoft's future to not be able to open maximized, LOL!

@miklevin commented on GitHub (Aug 19, 2019): Yes into a workaround. It's unreasonable for the main Microsoft Terminal app that's supposed to be a game changer and a big part of Microsoft's future to not be able to open maximized, LOL!
claunia commented 2026-01-30 23:19:06 +00:00
Author
Owner
Copy Link

@miklevin commented on GitHub (Aug 21, 2019):

Maybe just the option of opening in true Maximized from Settings. There naturally needs to be a way to open a Terminal app fullscreen.

@miklevin commented on GitHub (Aug 21, 2019): Maybe just the option of opening in true Maximized from Settings. There naturally needs to be a way to open a Terminal app fullscreen.
claunia commented 2026-01-30 23:19:06 +00:00
Author
Owner
Copy Link

@oblitum commented on GitHub (Aug 29, 2019):

Dude I have the same felling, I just downloaded the thing to try it out and my first impression was: where's fullscreen?!

@oblitum commented on GitHub (Aug 29, 2019): Dude I have the same felling, I just downloaded the thing to try it out and my first impression was: where's fullscreen?!
claunia commented 2026-01-30 23:19:06 +00:00
Author
Owner
Copy Link

@miklevin commented on GitHub (Sep 20, 2019):

Dude I have the same felling, I just downloaded the thing to try it out and my first impression was: where's fullscreen?!

How do I launch directly into fullscreen mode is the first thing any real terminal person is going to think, right? If the desktop shortcut isn't the way to go because of of packaging details, then surely they can add it to the preferences config file.

@miklevin commented on GitHub (Sep 20, 2019): > Dude I have the same felling, I just downloaded the thing to try it out and my first impression was: where's fullscreen?! How do I launch directly into fullscreen mode is the first thing any real terminal person is going to think, right? If the desktop shortcut isn't the way to go because of of packaging details, then surely they can add it to the preferences config file.
claunia commented 2026-01-30 23:19:06 +00:00
Author
Owner
Copy Link

@oblitum commented on GitHub (Sep 20, 2019):

@mikemaccana Alacritty works

@oblitum commented on GitHub (Sep 20, 2019): @mikemaccana [Alacritty works](https://github.com/microsoft/terminal/issues/531#issuecomment-531084700)
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 Needs-Tag-Fix Needs-Triage Resolution-External
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#3340
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?