3 ms·
3.4.0 adds support for $(foo) interpolation, which was the one thing that usually tripped me up when using basic provided scripts e.g. installation instructions
by robin_reala 5y ago
3.4.0 adds support for $(foo) interpolation, which was the one thing that usually tripped me up when using basic provided scripts e.g. installation instructions in READMEs. Fish previously only supported the (foo) syntax, without the dollar.
- deleted 5y ago[deleted]
- bin_bash 5y agoWhen they added support for && it really made my life easier with pasting snippets, happy to see this now as well
- eterps 5y agoAlso support for the 'export FOO=42' syntax helped a lot, with some care very simple scripts can be made to work both on fish and traditional shells
- ripley12 5y agoNice! I recently gave up on Fish after 3 years of using it as my primary shell. It was nice, but not nice enough to make up for all the pains of being different from POSIX shells. Glad to see Fish improving on that in a small but concrete way.
- theonemind 5y agoThe 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)