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
On windows, in pwsh.exe
pixi shell-hook
On windows in powershell, the command pixi shell-hook outputs batch script instead of the powershell commands.
The documentation seem to indicate that it should detect the shell it is running in.
Also, the shell names are here written in CamelCase, when they should have been lowercase names.
pixi shell-hook in powershell should output powershell script.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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
On windows, in pwsh.exe
Issue description
On windows in powershell, the command
pixi shell-hook
outputs batch script instead of the powershell commands.The documentation seem to indicate that it should detect the shell it is running in.
Also, the shell names are here written in CamelCase, when they should have been lowercase names.
Expected behavior
pixi shell-hook
in powershell should output powershell script.The text was updated successfully, but these errors were encountered: