News for hackers. Stuff that matters.
Re:Fish Shell Design Principles by creshal on Tuesday February 16, 2016 @06:07AM (#11109106)
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.
Re:Fish Shell Design Principles by dalore on Tuesday February 16, 2016 @07:14AM (#11109327)
There 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).
Re:Fish Shell Design Principles by StavrosK on Tuesday February 16, 2016 @08:23AM (#11109597)
I use virtualfish, which is even better:

https://github.com/adambrenecki/virtualfish

Re:Fish Shell Design Principles by ufo on Tuesday February 16, 2016 @09:52AM (#11110148)
99% 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)
Re:Fish Shell Design Principles by justinmayer on Tuesday February 16, 2016 @01:18PM (#11111909)
My Tacklebox/Tackle projects bundle Virtualfish, which addresses this very elegantly.

More info: https://hackercodex.com/guide/tacklebox-fish-shell/