-
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
Command line option to override alwaysOnTop #15375
Comments
You know, I dunno if we've ever given thought to something like Right now, we have For example, FWIW, these are all listed in |
I'm almost POSITIVE I had this in a thread or card or note somewhere. https://github.com/microsoft/terminal/projects/5#card-50760344 specifically mentions:
And I can't find 14 anywhere.... wait tho |
Thanks, that's great. I have WindowsTerminalPreview: 1.17.10234.0; --pos and --size work but I don't see them in |
Oops! I also have WindowsTerminal: 1.16.10261.0 (both unpackaged) and that's where wt.exe points (via AppPaths). Had I issued |
Wait but the docs with this should be live: https://github.com/MicrosoftDocs/terminal/blob/69955b0636de7a47f164019611d23745c6e046c3/TerminalDocs/command-line-arguments.md did I blow this away in MicrosoftDocs/terminal#649? Wait no it got blown away in MicrosoftDocs/terminal@b6e1ab9 Huh. |
I wish I could do the same for alwaysOnTop. I'm not crazy about devenv's "terminal". I have a lot of room in devenv and could easily tuck a small stay_on_top WT into a corner ... start it as an external tool. You can consider that a request ... alwaysOnTop command line option. Will that URL (preview's command line options) remain constant from version to version? |
Sure should. |
Is there a way to override these (maybe even others) when creating a new window?
-w -1 -M
and-w -1 -F
are limited versions of what I want to do.I've read a few (old) threads on specifying a settings file on the command line (valid only if creating a new window). That would seem to be the most robust way to override anything and I'm surprised it hasn't been implemented.
Another thought (hardly well thought-out) ... allow (possibly multiple) command line options like
--option (-o) global_option_name value
, again only for new windows.The text was updated successfully, but these errors were encountered: