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

Command line parameters need adjustments to run in PowerShell #5379

Closed
jdhitsolutions opened this issue Apr 16, 2020 · 2 comments
Closed

Command line parameters need adjustments to run in PowerShell #5379

jdhitsolutions opened this issue Apr 16, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jdhitsolutions
Copy link

Environment

Platform ServicePack Version      VersionString                    
-------- ----------- -------      -------------                    
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal 0.10.78.1.0

Any other software?

Steps to reproduce

I am trying out the command line examples. If I open a CMD window, and run this command

wt -p "Windows PowerShell No Profile"; split-pane -p "PowerShell 7 No Profile"

I get a new Terminal window with my two profiles vertically split. You can use any two profiles you want. This isn't a profile problem.

Expected behavior

When I run the same command in Windows PowerShell 5.1 or PowerShell 7 I expect or at least want the same result.

Actual behavior

Instead, I get the first profile in a new WT instance. When I close it, the next profile opens. PowerShell is treating the ; as an end of command marker so your example is actually two commands.

I think the command line option needs to be a single command that allows the user to specify the initial profile plus any additional customization such as split pane.

@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 Apr 16, 2020
@DHowett-MSFT
Copy link
Contributor

Thanks for the report! We have some documentation changes outstanding in #5361 and a lively discussion over in /dup #4570, so I'm gonna redirect discussion over there. Thanks!

@DHowett-MSFT DHowett-MSFT removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Apr 16, 2020
@ghost
Copy link

ghost commented Apr 16, 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 added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Tag-Fix Doesn't match tag requirements labels Apr 16, 2020
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