Pass Arguments to Start-Process with spaces

I would like to pass the powershell arguments to an process. The arguments may contain spaces.

Powershell Code:

$proc = Start-Process -FilePath "wsl.exe" -ArgumentList $args -NoNewWindow -PassThru
$proc | Wait-Process

Run Command

powershell -noprofile -executionpolicy bypass -file sh.ps1 bash -c "`"echo Hello World`""

No Output.

Running this command with static array works fine:

$proc = Start-Process -FilePath "wsl.exe" -ArgumentList @("bash", "-c", "`"echo Hello World`"") -NoNewWindow -PassThru
$proc | Wait-Process

Output

Hello World

What I needed todo to escape the arguments from the CLI args?

See https://github.com/PowerShell/PowerShell/issues/5576 why I have to escape spaces

<!-- language-all: sh -->

There's no good reason to use Start-Process in your case (see this GitHub docs issue for guidance on when Start-Process is and isn't appropriate).

Instead, use direct execution, which is not only synchronous and runs in the same console window (for console applications such as wsl.exe), but also allows you to directly capture or redirect output.

In doing so, you'll also be bypassing the longstanding Start-Process bug you mention (GitHub issue #5576), because PowerShell double-quotes arguments passed to external programs as needed behind the scenes (namely if they contain spaces).

$exe, $exeArgs = $args   # split argument array into exe and pass-thru args
wsl.exe -e $exe $exeArgs # execute synchronously, via wsl -e 

Note that you then also don't need to embed escaped " in your PowerShell CLI call:

powershell -noprofile -executionpolicy bypass -file sh.ps1 bash -c "echo Hello World"

However, if your arguments truly needed embedded ", you'd run into another longstanding PowerShell bug that affects only direct invocation of external programs, necessitating manual escaping with \ - see this answer.

If you do need to use Start-Process - e.g. if you want the process to run in a new (console) window - you'll have to provide embedded quoting around those $args elements that need it, along the following lines:

$quotedArgs = foreach ($arg in $args) {
  if ($arg -notmatch '[ "]') { $arg }
  else { # must double-quote
    '"{0}"' -f ($arg -replace '"', '\"' -replace '\$', '\\')
  }
}

$proc = Start-Process -FilePath "wsl.exe" -ArgumentList $quotedArgs -PassThru
$proc | Wait-Process


</details>



# 答案2
**得分**: 0

显而易见的答案是，使用`$myargs`作为字符串数组。 "echo Hello World" 需要嵌入的双引号（或单引号）来包裹它，这会使事情变得复杂。

```powershell
$myargs = "bash", "-c", "'echo Hello World'"
$proc = Start-Process -FilePath wsl.exe -ArgumentList $myargs -NoNewWindow -PassThru
$proc | Wait-Process

Hello World

我会这样做：

.\sh.ps1 bash -c 'echo hello world'

# sh.ps1 包含：
# wsl $args

或者对于 Windows 上的 WSL bash：

bash -c 'echo hello world'

我碰巧在 WSL 中安装了 pwsh。没有单引号，每个单词将被放在新行上。

wsl pwsh -c "echo 'hello world'"

这对我来说在另一个 PowerShell 中也有效，其中有另一组嵌入的引号：

powershell -noprofile -executionpolicy bypass -file sh.ps1 bash -c "`'echo Hello World`'"

$myargs = "bash", "-c", "'echo Hello World'"
$proc = Start-Process -FilePath wsl.exe -ArgumentList $myargs -NoNewWindow -PassThru
$proc | Wait-Process

Hello World

.\sh.ps1 bash -c 'echo hello world'

# sh.ps1 contains:
# wsl $args

bash -c 'echo hello world'

wsl pwsh -c "echo 'hello world'"

powershell -noprofile -executionpolicy bypass -file sh.ps1 bash -c "`"'echo Hello World'`""