3 ms·
One of my users is using fish in an otherwise zsh-only environment, so far we've only ran into problems once: virtualenv's activate script needs to be shell-spe
by creshal 11y ago
One of my users is using fish in an otherwise zsh-only environment, so far we've only ran into problems once: virtualenv's activate script needs to be shell-specific to muck around with env variables. Every other tooling we use for webdev (npm, bower, whatever the kids are using now to pretend make doesn't exist, …) runs without problem.
- justinmayer 11y agoMy Tacklebox/Tackle projects bundle Virtualfish, which addresses this very elegantly. More info: https://hackercodex.com/guide/tacklebox-fish-shell/ https://hackercodex.com/guide/tacklebox-fish-shell/
- dalore 11y agoThere is activate.fish provided by virtualenv. In case you didn't already know (you didn't menation, thought it might be good to let others know if they see this).
- StavrosK 11y agoI use virtualfish, which is even better: https://github.com/adambrenecki/virtualfish https://github.com/adambrenecki/virtualfish
- ufo 11y ago99% of shell scripts are just executables that have a shebang line at the top. As a rule of thumb, the only time when using a posix-compatible shell as your interactive shell matters is when you are expected to "source" or "eval" a sh script that is generated by some other program (as the virtualenv example)