We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
pixi --version
Add-Content -Path $PROFILE -Value 'Invoke-Expression (&pixi completion --shell powershell)'
This has two problems:
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
Completions to work :)
The text was updated successfully, but these errors were encountered:
The right way to register completions for pwsh is adding this to your $PROFILE:
$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'
Sorry, something went wrong.
@chawyehsu nice! Would you be able to create a PR to update the install script?
#325 ready
Can confirm that this solves the issue.
No branches or pull requests
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
Issue description
This has two problems:
Could reproduce with powershell 6 and 7
Expected behavior
Completions to work :)
The text was updated successfully, but these errors were encountered: