5 ms·

Copy and pasted from another reply: "I still wish fish support && and ||, if only for the times when I copy and paste some one-liner off of stack overflow and h

by jhasse 9y ago

Copy and pasted from another reply: "I still wish fish support && and ||, if only for the times when I copy and paste some one-liner off of stack overflow and have to rewrite it." That and support for SOME_ENV_VAR=foo ./bar (not having to prepend "env ") are what's stopping me from recommending fish to others. Btw: Big thank you for fish, it's awesome!

mattgreenrocks 9y ago
Yes please, even if we have to opt in to this behavior with a patronizing env var :)
nonsince 9y ago
I really like that you have to use `env` in fish, since it's cross-shell - it works in bash/zsh/dash/whatever. The `A=b foo` syntax is an unnecessary appendix in the syntax that complicates matters while only saving 4 characters.
- jhasse 9y ago
  I agree and think the best fix would be if the syntax would be forbidden in bash/zsh. Problem is: Millions of code snippets on the Internet not using env.
  - nine_k 9y ago
    For one-liners, typing `env ` before pasting is likely not too much work. For longer scripts, you'd have to rewrite much of the text anyway.
    - jhasse 9y ago
      often there's stuff like cd build && LD_LIBRARY_PATH=../lib ./foo :/ It's no dealbreaker though, I still use fish and love it :) Just a minor annoyance ;)
- vram22 9y ago
  That syntax is from very early days of sh itself (predecessor of bash), IIRC. So removing it would break many scripts, as sibling comment by jhasse said.
- Pete_D 9y ago
  It's not just to save typing - having an `A=b foo` form built-in instead of relying on an external program means `foo` can be an alias or shell function.
knutae 9y ago
Agree with these, and would like to add one more: $(subcommand) as an alternative to (subcommand) PS: I have been using fish as my primary shell for about a year now, very happy with it. :)
- jhasse 9y ago
  Good news: Another dev mentioned that they are already discussing this: https://news.ycombinator.com/item?id=15913358 https://news.ycombinator.com/item?id=15913358

by jhasse 9y ago

mattgreenrocks 9y ago

Yes please, even if we have to opt in to this behavior with a patronizing env var :)

nonsince 9y ago

I really like that you have to use `env` in fish, since it's cross-shell - it works in bash/zsh/dash/whatever. The `A=b foo` syntax is an unnecessary appendix in the syntax that complicates matters while only saving 4 characters.

jhasse 9y ago
I agree and think the best fix would be if the syntax would be forbidden in bash/zsh. Problem is: Millions of code snippets on the Internet not using env.
- nine_k 9y ago
  For one-liners, typing `env ` before pasting is likely not too much work. For longer scripts, you'd have to rewrite much of the text anyway.
  - jhasse 9y ago
    often there's stuff like cd build && LD_LIBRARY_PATH=../lib ./foo :/ It's no dealbreaker though, I still use fish and love it :) Just a minor annoyance ;)
vram22 9y ago
That syntax is from very early days of sh itself (predecessor of bash), IIRC. So removing it would break many scripts, as sibling comment by jhasse said.
Pete_D 9y ago
It's not just to save typing - having an `A=b foo` form built-in instead of relying on an external program means `foo` can be an alias or shell function.

knutae 9y ago

Agree with these, and would like to add one more: $(subcommand) as an alternative to (subcommand) PS: I have been using fish as my primary shell for about a year now, very happy with it. :)

jhasse 9y ago
Good news: Another dev mentioned that they are already discussing this: https://news.ycombinator.com/item?id=15913358 https://news.ycombinator.com/item?id=15913358