4 ms·
Fish is the shell I wish I could use, but I'm afraid of the tinkering I have to do to get common tools and workflows to work.
by threatofrain 11y ago
Fish is the shell I wish I could use, but I'm afraid of the tinkering I have to do to get common tools and workflows to work.
- qznc 11y agoWhat do you mean? The main limitation I know of is tab-completion.
- hundkex 11y agoBass might provide some help with that. https://github.com/edc/bass https://github.com/edc/bass
- cmrx64 11y agoI transitioned from zsh without any hassle, though I did need to port my environment variable config.
- flohofwoe 11y agoFish works great in everyday use, especially the 'smart completion'. I didn't encounter shell scripts that wouldn't work in fish, since they don't run though fish, but sh or bash. Naturally some bash things don't work on the command line (for instance backticks), for these I usually quickly jump into a bash session, run the bash expressions, and then go back to fish.
- oranjax 11y agofish simply replaced `backticks` with (parentheses). give it a go.
- ajsalminen 11y agoBackticks aren't recommended even in POSIX anymore, $() is the newer, preferred alternative.
- 0942v8653 11y agoHuh? Does sh have "$()"? I thought we had to use backticks for POSIX-only environments.
- cmrx64 11y agoYes, POSIX sh has $(): 2.6.3 Command Substitution (http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu...)
- jon-wood 11y agoI spent a long time feeling that way too, and then took the job one day. Turns out its generally fine - I had a bit of pain getting NVM to work, but otherwise its been really smooth.
- bucaran 11y agoTry it with Bass, it works fine for me. Although, recently I switched to tj/n, which has a nicer CLI in my opinion. + https://github.com/edc/bass#example https://github.com/edc/bass#example
- creshal 11y agoOne 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)
- spinningarrow 11y agoJust take the plunge! Support for popular tools is better than it used to be. I've been using it for a few years now and it's been quite a while since I faced any sort of issues. It's subjective of course, based on what your workflows are and how much bash-fu they involve.