News for hackers. Stuff that matters.
Re:Fish shell by eridius on Monday May 18, 2015 @06:20PM (#9567182)
That's a different problem, though. /bin/sh must point to a sh-compatible shell. fish is not a sh-compatible shell. Therefore, any script using /bin/sh will never attempt to run as fish (as /bin/sh will never point to fish).

The reason I'm having a hard time imagining how a scripting system that relies on bash would fail with fish is because I can't imagine how one would actually write a script that is executed with the user's login shell. There's no #! line that would do that by accident.

Re:Fish shell by rquirk on Tuesday May 19, 2015 @07:42AM (#9569294)
There's just one scenario: a completely absent #! line.

It's an easy fix, just add the line, otherwise 0755 scripts with no #! do execute using the current shell.

Re:Fish shell by eridius on Tuesday May 19, 2015 @02:49PM (#9572247)
That doesn't work for me (in Fish).

  > cat foo
  echo wat
  > ./foo
  Failed to execute process './foo'. Reason:
  exec: Exec format error
  The file './foo' is marked as an executable but could not be run by the operating system.
It does however work in Bash. So this appears to be a bash-ism, rather than an OS feature.
Re:Fish shell by rquirk on Wednesday May 20, 2015 @11:32AM (#9576978)
Ah, bummer. I tested in csh too but not fish.