4 ms·
The old behavior amused me. There's probably a decent argument for it, but it's kind of infuriating: theonemind@onemindsmachine ~> echo $(badfish) fish: $(...)
by theonemind 5y ago
The old behavior amused me. There's probably a decent argument for it, but it's kind of infuriating:
theonemind@onemindsmachine ~> echo $(badfish)
fish: $(...) is not supported. In fish, please use '(badfish)'.
echo $(badfish)
^
"I know exactly what you meant. Not gonna do it."
- em-bee 5y ago`echo (goodfish)` just looks a lot cleaner to me. and as i am still using other shells some times (can't install fish on all my clients machines) the visual difference between `()` and `$()` helps to make it more obvious which shell i am currently using.
- saghm 5y agoSeems like just printing a warning to stderr or something would be a reasonable behavior (or even just printing to the screen when interactive in some special way that doesn't go to stdout or stderr in order to not mess up scripts)