Fish is supported?

[hedefalk]

Originally reported here because I thought it was zed's fault (because I seldom just start a fish from my fish): zed-industries/zed#21269 (comment)

I'm on Macos with nix-darwin and fish is my default shell. To reproduce:

mkdir new-devenv-scaffold
cd new-devenv-scaffold/
devenv init

then just

>fish

🐟fish
bash: line 6: compgen: command not found
set: Tried to modify the special variable 'PWD' with the wrong scope
set: Tried to modify the special variable 'SHLVL' with the wrong scope
warning: Could not set up terminal.
warning: TERM environment variable not set.
warning: Using fallback terminal type 'xterm-256color'.
warning: Could not set up terminal.
warning: TERM environment variable not set.
warning: Using fallback terminal type 'xterm-256color'.
/nix/store/sk8z3kdy6iaky6sg972k6fkh3iw2rn3d-bash-5.2p37/bin/bash: line 1: env: command not found
Error: $HOME must be set to run brew.
fish: Unknown command: starship
/Users/viktor/.config/fish/config.fish (line 25):
starship init fish | source
^~~~~~~^
from sourcing file /Users/viktor/.config/fish/config.fish
        called during startup
/nix/store/mmwqalliqz09swrrgiy8r4sf95v51rdq-any-nix-shell-2.0.1/bin/.any-nix-shell-wrapped: line 55: cat: command not found
/Users/viktor/dev/lightbend/kalix/infra-aws/scripts/aws-auth-functions.sh: line 8: dirname: command not found
bash: line 6: awk: command not found
bash: line 6: awk: command not found
bash: line 6: awk: command not found
direnv: error couldn't find a cache directory for direnv
@studio ~/U/v/d/z/new-devenv-scaffold (main)> exit

So some bashism here that I don't fully understand…

A simple direnv with a flake is working fine, but as soon as I introduced devenv into my mix this happens.

[hedefalk]

Note, I've added:

impure: true

to the deveny.yaml, forgot to write that. In my original use I had "use flake --impure" in the .envrc instead.

[sandydoo]

I use fish as my default shell and I have not experienced anything like this.

I would try running printenv in the shell you get before trying to launch fish. From the error log, it seems like your shell is missing a lot of important environment variables.

And if you're using direnv to activate the shell, there's not need to launch another instance of fish. direnv modifies your environment in situ.