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

Allow command line(s) without specifying the executable #7289

Closed
rubinusp opened this issue Aug 14, 2020 · 2 comments
Closed

Allow command line(s) without specifying the executable #7289

rubinusp opened this issue Aug 14, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@rubinusp
Copy link

rubinusp commented Aug 14, 2020

Right now, the commandline setting of Profile is only for executable. It has been a trick to add command lines as arguments to the executable. But it adds higher complexity to the whole statement. For those profiles that have source, it is nice if commandline functions as the launching command lines without specifying the executable. It is a useful feature to automatically set up and open a docker environment in the terminal, or switching as admin.

Example
{
"guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
"hidden": false,
"name": "Ubuntu",
"source": "Windows.Terminal.Wsl",
"colorScheme": "UbuntuLegit",
"commandline": "sudo -s"
}

This will automatically launch the shell as the root user.

@rubinusp rubinusp added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 14, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 14, 2020
@rubinusp rubinusp changed the title Allow command line(s) to run automatically on launch Allow command line(s) without specifying the executable Aug 14, 2020
@DHowett
Copy link
Member

DHowett commented Aug 18, 2020

Thanks for the request! This is largely a /duplicate of #5528/#5571 so I'd like to consolidate discussion there.

@ghost
Copy link

ghost commented Aug 18, 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 Aug 18, 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 Aug 18, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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