doc: Add note about using ; as a separator in PowerShell#5361
doc: Add note about using ; as a separator in PowerShell#5361DHowett-MSFT merged 6 commits intomasterfrom
; as a separator in PowerShell#5361Conversation
Co-Authored-By: Dustin L. Howett (MSFT) <duhowett@microsoft.com>
|
|
||
| #### Single quoted parameters (if you aren't calculating anything): | ||
| In this example, we'll wrap all the parameters to `wt` in single quotes (`'`), | ||
| and run `wt` with the `Start-Process` command: |
There was a problem hiding this comment.
nit: add a sentence about what start-process does.
|
|
||
| #### Not using `start` | ||
|
|
||
| The astute reader will note that all the above examples used `start` to launch the Terminal. |
There was a problem hiding this comment.
eh. We could probably do without this statement.
There was a problem hiding this comment.
As a counterpoint? I saw start and wondered "wtf is he using start for over and over"
There was a problem hiding this comment.
Ah. By "statement" I mean this specific sentence, not section. Feels a bit weird to call the reader "astute" haha.
There was a problem hiding this comment.
no, i mean, i specifically noticed that start was in use, and I wanted to know why. I think this sentence is valuable because it makes people feel seen ;P
There was a problem hiding this comment.
Um.... It's probably worth noting that start avoids the waiting problem described below.
| ``` | ||
|
|
||
| ```Powershell | ||
| wt --% new-tab cmd ; split-pane -p "Windows PowerShell" ; split-pane -H wsl.exe |
There was a problem hiding this comment.
Wouldn't you be able to mix this with start and do something like start --% wt ...? Then you get the best of both worlds.
There was a problem hiding this comment.
start-process doesn't quite work like that
Co-Authored-By: Josh Soref <jsoref@users.noreply.github.com>
|
@carlos-zamora your concerns have been addressed? |
; as a separator for wt commands in Powershell; as a separator in PowerShell
This PR adds some notes from #4570 to the UsingCommandlineArguments.md doc. Hopefully, this should add clarity on how to use sub-commands in the
wtcommandline from within Powershell.;for separating subcommands #4570