Powershell completions broken

[Hofer-Julian]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

Add-Content -Path $PROFILE -Value 'Invoke-Expression (&pixi completion --shell powershell)'

Issue description

This has two problems:

• It doesn't add a newline beforehand, which will not work if your profile isn't empty
• If that is fixed it still fails with the following when starting up powershell:

Invoke-Expression : Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'Command'. Specified method is not supported.
At C:\Users\hofer_jn\OneDrive - Stichting Deltares\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1:1 char:19
+ Invoke-Expression (&pixi completion --shell powershell)
+                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Invoke-Expression], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgument,Microsoft.PowerShell.Commands.InvokeExpressionCommand

Could reproduce with powershell 6 and 7

Expected behavior

Completions to work :)

[chawyehsu]

The right way to register completions for pwsh is adding this to your $PROFILE:

(& pixi completion --shell powershell) | Out-String | Invoke-Expression

or by running:

Add-Content -Path $PROFILE -Value '(& pixi completion --shell powershell) | Out-String | Invoke-Expression'

[baszalmstra]

@chawyehsu nice! Would you be able to create a PR to update the install script?

[chawyehsu]

#325 ready

[Hofer-Julian]

Can confirm that this solves the issue.