initialPosition (and others) should be available as commandline args #6488

Closed
opened 2026-01-31 00:40:07 +00:00 by claunia · 13 comments
Owner

Originally created by @bruceoberg on GitHub (Feb 17, 2020).

initial issue description mentions "per-profile", but consider that they could be commandline arguments

Description of the new feature/enhancement

i want to create multiple shortcuts that launch wt at different sizes and screen positions. i'm talking about multiple instances of wt, not multiple tabs within wt.

however, the initialPosition setting is global and cannot be overridden on a per-profile basis. ditto for initialRows, initialCols and launchMode. because these are global settings, any shortcut can only launch wt at one position and size.

i'm looking for parity with CMD here. a shortcut to CMD has a bunch of settings tabs, including screen size and position. i have shortcuts to launch CMD in different places for various reasons. i'd like to use shortcuts to launch wt instead.

Proposed technical implementation details (optional)

allow initialPosition, initialRows, initialCols and launchMode to be specified within a profile in settings.json. if that profile is the main one active at launch time, then use them instead of the globals.

Originally created by @bruceoberg on GitHub (Feb 17, 2020). _initial issue description mentions "per-profile", but consider that they could be commandline arguments_ # Description of the new feature/enhancement i want to create multiple shortcuts that launch wt at different sizes and screen positions. i'm talking about multiple instances of wt, not multiple tabs within wt. however, the `initialPosition` setting is global and cannot be overridden on a per-profile basis. ditto for `initialRows`, `initialCols` and `launchMode`. because these are global settings, any shortcut can only launch wt at one position and size. i'm looking for parity with CMD here. a shortcut to CMD has a bunch of settings tabs, including screen size and position. i have shortcuts to launch CMD in different places for various reasons. i'd like to use shortcuts to launch wt instead. # Proposed technical implementation details (optional) allow `initialPosition`, `initialRows`, `initialCols` and `launchMode` to be specified within a profile in settings.json. if that profile is the main one active at launch time, then use them instead of the globals.
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

I'd prefer to let commandline arguments solve this one, honestly. I don't like the idea of profiles whose settings override application-level settings, because that opens up a pretty big can of worms.
To that end, I've renamed this. Please feel free to complain: I want to make sure I'm not shutting down valuable discussion here.

@DHowett-MSFT commented on GitHub (Feb 21, 2020): I'd prefer to let commandline arguments solve this one, honestly. I don't like the idea of profiles whose settings override application-level settings, because that opens up a pretty big can of worms. To that end, I've renamed this. Please feel free to complain: I want to make sure I'm not shutting down valuable discussion here.
Author
Owner

@bruceoberg commented on GitHub (Feb 22, 2020):

command line arguments is a fine solution. i would have no complaints.

@bruceoberg commented on GitHub (Feb 22, 2020): command line arguments is a fine solution. i would have no complaints.
Author
Owner

@dpokluda commented on GitHub (Feb 25, 2020):

+1 command line arguments would work for me as well

@dpokluda commented on GitHub (Feb 25, 2020): +1 command line arguments would work for me as well
Author
Owner

@bruceoberg commented on GitHub (Jan 17, 2021):

i think the strongest reason for this is that CMD has it and i depend on the feature. @DHowett-MSFT @cinnamon-msft should i be trying to write this myself and then send a PR? i can't what sort of priority this request has.

@bruceoberg commented on GitHub (Jan 17, 2021): i think the strongest reason for this is that CMD has it and i depend on the feature. @DHowett-MSFT @cinnamon-msft should i be trying to write this myself and then send a PR? i can't what sort of priority this request has.
Author
Owner

@DHowett commented on GitHub (Jan 17, 2021):

@bruceoberg cmd has a feature where you can specify the initial position by commandline argument?

As the engineering owner for cmd, I'm surprised to hear that. Do you have any more details?

@DHowett commented on GitHub (Jan 17, 2021): @bruceoberg cmd has a feature where you can specify the initial position by commandline argument? As the engineering owner for cmd, I'm surprised to hear that. Do you have any more details?
Author
Owner

@DHowett commented on GitHub (Jan 17, 2021):

Oh, I see. Per-profile. It doesn't really have that: it's per shortcut file or exe, for which the equivalent is a terminal shortcut that spawns wt with arguments. We are not introducing launch settings to profiles, because they don't make sense at that level. Sorry.

@DHowett commented on GitHub (Jan 17, 2021): Oh, I see. Per-profile. It doesn't _really_ have that: it's per shortcut file or exe, for which the equivalent is a terminal shortcut that spawns wt with arguments. We are not introducing launch settings to profiles, because they _don't make sense at that level_. Sorry.
Author
Owner

@DHowett commented on GitHub (Jan 17, 2021):

(i got tricked by my own re-titling of your issue. Sorry about that!)

@DHowett commented on GitHub (Jan 17, 2021): (i got tricked by my own re-titling of your issue. Sorry about that!)
Author
Owner

@bruceoberg commented on GitHub (Mar 15, 2021):

so i will never be able to create two shortcuts that launch two wt instances in two different positions? i don't need per-profile settings, i just need a command-line option to set the position and size.

@bruceoberg commented on GitHub (Mar 15, 2021): so i will never be able to create two shortcuts that launch two wt instances in two different positions? i don't need per-profile settings, i just need a command-line option to set the position and size.
Author
Owner

@zadjii-msft commented on GitHub (Mar 16, 2021):

I don't think anyone ever said that - DHowett just confused himself 😆

We definitely want to add --initialPostition, --initialRows, --initialCols to the commandline arguments available. Then, you could use those in a shortcut to set the position and size of the Terminal.

@zadjii-msft commented on GitHub (Mar 16, 2021): I don't think anyone ever said that - DHowett just confused himself 😆 We definitely want to add `--initialPostition`, `--initialRows`, `--initialCols` to the commandline arguments available. Then, you could use those in a shortcut to set the position and size of the Terminal.
Author
Owner

@arkanario commented on GitHub (Nov 1, 2021):

Any news on this subject?

How to start a new windows terminal from command line in a specific location and with specific window size?

@arkanario commented on GitHub (Nov 1, 2021): Any news on this subject? How to start a new windows terminal from command line in a specific location and with specific window size?
Author
Owner

@zadjii-msft commented on GitHub (Nov 1, 2021):

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?
image
That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

@zadjii-msft commented on GitHub (Nov 1, 2021): Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? ![image](https://user-images.githubusercontent.com/18356694/91237459-5cbb0c80-e700-11ea-9347-b9b1ec2813b1.png) That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️
Author
Owner

@zadjii-msft commented on GitHub (Jun 15, 2022):

Notes from #13307: Make sure there's a sentinel value or flag or something to also allow CW_USEDEFAULT as the position

@zadjii-msft commented on GitHub (Jun 15, 2022): Notes from #13307: Make sure there's a sentinel value or flag or something to also allow `CW_USEDEFAULT` as the position
Author
Owner

@ghost commented on GitHub (Jan 24, 2023):

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

Handy links:

@ghost commented on GitHub (Jan 24, 2023): :tada:This issue was addressed in #13730, which has now been successfully released as `Windows Terminal Preview v1.17.1023`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.17.1023) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6488