News for hackers. Stuff that matters.
Re:Fish Shell Design Principles by flohofwoe on Tuesday February 16, 2016 @05:26AM (#11108954)
Fish 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.
Re:Fish Shell Design Principles by oranjax on Tuesday February 16, 2016 @05:43AM (#11109005)
fish simply replaced `backticks` with (parentheses). give it a go.
Re:Fish Shell Design Principles by ajsalminen on Tuesday February 16, 2016 @06:22AM (#11109148)
Backticks aren't recommended even in POSIX anymore, $() is the newer, preferred alternative.
Re:Fish Shell Design Principles by 0942v8653 on Tuesday February 16, 2016 @07:05AM (#11109304)
Huh? Does sh have "$()"? I thought we had to use backticks for POSIX-only environments.
Re:Fish Shell Design Principles by cmrx64 on Tuesday February 16, 2016 @09:17AM (#11109895)
Yes, POSIX sh has $(): 2.6.3 Command Substitution (http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu...)