Skip to content
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

Hidden profiles cannot be specified with -p tag from command line. #8378

Closed
jmahlers opened this issue Nov 23, 2020 · 3 comments
Closed

Hidden profiles cannot be specified with -p tag from command line. #8378

jmahlers opened this issue Nov 23, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jmahlers
Copy link

jmahlers commented Nov 23, 2020

Environment

Microsoft Windows [Version 10.0.19042.630]
Windows Terminal
Version: 1.4.3243.0

WSL Ubuntu and others but not relevant.

Steps to reproduce

Create a profile for example:

{
                "guid": "{00000000-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command-Prompt-In-Place",
                "commandline": "cmd.exe",
                "startingDirectory": ".",
                "hidden": true
}

Then, attempt to create an instance of windows terminal from the command line with this profile ie:

wt.exe -p "Command-Prompt-In-Place"

Expected behavior

The specified profile should be chosen. This is useful so that a profile can be triggered by a command that isn't taking up space in the drop down in the app. One example is so that the default profile can start in some useful directory "C:\src" while an otherwise identical profile can start in ".". This is useful because then a profile can start in the current directory without taking up space in the menus. I am using this so I can right click and have "Open windows terminal here" in the context menu. Obviously the profile for "Open windows terminal here" is not needed in the menus.

Actual behavior

The hidden profile is not targetable and the default profile is chosen.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 23, 2020
@DHowett
Copy link
Member

DHowett commented Nov 23, 2020

You're in luck! This was fixed in 1.5 (currently in preview) and is a /duplicate of #4139

@ghost
Copy link

ghost commented Nov 23, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Nov 23, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 23, 2020
@jmahlers
Copy link
Author

Awesome, sorry I didnt find that before. Thanks!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants