-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
initialPosition (and others) should be available as commandline args #4620
Comments
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. |
command line arguments is a fine solution. i would have no complaints. |
+1 command line arguments would work for me as well |
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 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? |
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. |
(i got tricked by my own re-titling of your issue. Sorry about that!) |
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. |
I don't think anyone ever said that - DHowett just confused himself 😆 We definitely want to add |
Any news on this subject? How to start a new windows terminal from command line in a specific location and with specific window size? |
Notes from #13307: Make sure there's a sentinel value or flag or something to also allow |
🎉This issue was addressed in #13730, which has now been successfully released as Handy links: |
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 forinitialRows
,initialCols
andlaunchMode
. 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
andlaunchMode
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.The text was updated successfully, but these errors were encountered: