You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just discovered that eval (pixi shell-hook) does not work properly, as it only sets the path. The proper workaround is to run pixi shell-hook | source.
BTW, since I use starship for my shell prompt. This will actually properly display the pixi environment in the propmpt, even though the shell snippet doesn't actually modify the fish prompt explicitly.
Apparently both pixi shell and starship init fish overwrite the function fish_prompt. We should look into how to avoid that overwrite in fish. Maybe @tdejager knows some tricks?
eval "$(pixi shell-hook)" works but the | source is advised as the shell-hook doesn't need stdin
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
When running
pixi shell
, I get an error about invalid fish syntax. Runningeval (pixi shell-hook)
works as expected.It appears that the issue only happens when setting the prompt, which is not modified by
pixi shell-hook
, so that's probably why it works.Expected behavior
I should get a pixi environment shell without an error.
The text was updated successfully, but these errors were encountered: