5 ms·

Don't have anything to add to this except to say thanks to the team for an amazing product. Been using fish shell for 5+ years now and I love it. "Finally, a co

Don't have anything to add to this except to say thanks to the team for an amazing product. Been using fish shell for 5+ years now and I love it. "Finally, a command line shell for the 90s"!

drcongo 6y ago
I'd like to echo that, I _love_ fish. This looks like a huge release from the changelog.
joseluisq 6y ago
Many of us use it, I personally in my daily basis development Fish shell is pretty neat and increases productivity in terminal. However I still use Bash in the server side where I need for example, explicit error aborting like `set -e` that Fish doesn't have yet. https://github.com/fish-shell/fish-shell/issues/510 https://github.com/fish-shell/fish-shell/issues/510
- Siecje 6y ago
  set -e is not great and is not recommended. http://mywiki.wooledge.org/BashFAQ/105 http://mywiki.wooledge.org/BashFAQ/105
  - joseluisq 6y ago
    Agree with the "false positives" however in combination with error handling I don't see why not use it.
  - _jal 6y ago
    -e is in the class of things that can be fine to use, but the people least-likely to be prepared to know when it can be are the most likely to expect it to behave better than it does. Sort of a combination finger-trap/cigar cutter for newbies.
    - joseluisq 6y ago
      Yeah.. but still useful despite the "false positives" that the link states which are addressable with proper error handling.
      - tadfisher 6y ago
        `-eu -o pipefail` catches most of what newcomers expect anyway.
  - rgoulter 6y ago
    I read this as "bash has unintuitive footguns" rather than "set -e has unintuitive footguns with its usage".
    - oblio 6y ago
      Bash doesn't have unintuitive footguns, bash <<is>> a unintuitive footgun :-)
  - t0astbread 6y ago
    I agree with the second to last recommendation: > rking's personal recommendation is to go ahead and use set -e, but beware of possible gotchas. It has useful semantics, so to exclude it from the toolbox is to give into FUD. Manual error handling would be ideal but it's too easy for me to mess up and miss something. Plus, if you really wanted to catch everything with proper error handling you would need to wrap every command in your script.
- giantandroids 6y ago
  if you use a bash shebang in your scripts, does it not matter (honest question, I never have used fish)?

Don't have anything to add to this except to say thanks to the team for an amazing product. Been using fish shell for 5+ years now and I love it. "Finally, a command line shell for the 90s"!

drcongo 6y ago

I'd like to echo that, I _love_ fish. This looks like a huge release from the changelog.

joseluisq 6y ago

Many of us use it, I personally in my daily basis development Fish shell is pretty neat and increases productivity in terminal. However I still use Bash in the server side where I need for example, explicit error aborting like `set -e` that Fish doesn't have yet. https://github.com/fish-shell/fish-shell/issues/510 https://github.com/fish-shell/fish-shell/issues/510

Siecje 6y ago
set -e is not great and is not recommended. http://mywiki.wooledge.org/BashFAQ/105 http://mywiki.wooledge.org/BashFAQ/105
- joseluisq 6y ago
  Agree with the "false positives" however in combination with error handling I don't see why not use it.
- _jal 6y ago
  -e is in the class of things that can be fine to use, but the people least-likely to be prepared to know when it can be are the most likely to expect it to behave better than it does. Sort of a combination finger-trap/cigar cutter for newbies.
  - joseluisq 6y ago
    Yeah.. but still useful despite the "false positives" that the link states which are addressable with proper error handling.
    - tadfisher 6y ago
      `-eu -o pipefail` catches most of what newcomers expect anyway.
- rgoulter 6y ago
  I read this as "bash has unintuitive footguns" rather than "set -e has unintuitive footguns with its usage".
  - oblio 6y ago
    Bash doesn't have unintuitive footguns, bash <<is>> a unintuitive footgun :-)
- t0astbread 6y ago
  I agree with the second to last recommendation: > rking's personal recommendation is to go ahead and use set -e, but beware of possible gotchas. It has useful semantics, so to exclude it from the toolbox is to give into FUD. Manual error handling would be ideal but it's too easy for me to mess up and miss something. Plus, if you really wanted to catch everything with proper error handling you would need to wrap every command in your script.
giantandroids 6y ago
if you use a bash shebang in your scripts, does it not matter (honest question, I never have used fish)?