Closed agentultra closed 5 years ago
Thanks for the report. I don't use Fish myself, but if someone can suggest a fix for this I'd be happy to incorporate it.
It looks like if you remove the "-i"
from the shell arguments it works.
Hopefully 76cd6e3 will help - perhaps you could confirm and close this issue if so?
It does, cheers!
I'm running Arch Linux where the recommended way to start fish is to use bash as your default shell but to add exec fish
to your .bashrc. Even with this commit I was getting errors until I used the alternate implementation listed in ArchWiki:
- To have commands such as bash -c 'echo test' run the command in Bash instead of starting fish, you can write if [ -z "$BASH_EXECUTION_STRING" ]; then exec fish; fi instead.
I'm running Arch Linux where the recommended way to start fish is to use bash as your default shell but to add
exec fish
to your .bashrc. Even with this commit I was getting errors until I used the alternate implementation listed in ArchWiki:
I guess then you'd have to decide between setting your env vars in the bash startup files or the fish ones. It then begs the question of which "your" $SHELL really is. If you set things up this way, I'd imagine you'd put env vars in the bash startup files, and your shell would be bash
as far as Emacs is concerned. And in that case, you should be avoiding including -i
in exec-path-from-shell-arguments
, as noted in the docs, which would prevent bash from even executing .bashrc
.
Yep, I ended up moving my env vars over to .bashrc along with the above.
I'm using spacemacs and am not sure how to modify how it invokes exec-path-from-shell, but it seems to work fine for now.
Thanks!
Fish seems to have changed how it execs jobs to the foreground which breaks with how exec-path-from-shell invokes fish:
MacOS 10.12.6, Fish 3.0.0, Emacs 26.1+