strict_errexit message missing code location

[ale5000-git]

I'm using ysh from here: https://op.oilshell.org/uuu/github-jobs/8206/cpp-tarball.wwz/_release/oils-for-unix.tar

I was trying to run this script with ysh: https://github.com/micro5k/microg-unofficial-installer/blob/main/tools/bits-info.sh
and the only thing it say is this:
[??? no location ???] fatal: strict_errexit only allows simple commands in conditionals (got command.Redirect).

I think it should at least say the line number.

[andychu]

Thanks for the report - I improved the message to look like this

$ bin/ysh bits-info.sh 
  {
  ^
bits-info.sh:19: fatal: Command conditionals should only have one status, not BraceGroup (strict_errexit, OILS-ERR-300)

OILS-ERR-300 refers to a new message in the error catalog, which will be rendered shortly

http://op.oilshell.org/uuu/github-jobs/8214/

[andychu]

There is a long doc about out error handling philosophy, which is explicit and is designed not to lose any exit codes

http://www.oilshell.org/release/0.23.0/doc/error-handling.html

{
  command 1> /dev/null -v ':'
} 2> /dev/null || command()

Hm arguably it could be relaxed for this case, because there is only one command.

The problem is when the {} contains two commands - it is ambiguous. Not sure if that is possibel though

---

I think that statement can be written

command -v ':' 1>/dev/null 2>/dev/null 

that is probably the same thing

$ command zz
-bash: zz: command not found

$ command 2>/dev/null zz

[ale5000-git]

The problem is that the shell that don't support command actually print the error outside the command so command -v ':' 1>/dev/null 2>/dev/null don't hide the error.

Initially the check was command -v command but then another shell (hush) fail because command can't check itself there (most likely a bug) so I have changed it to check : that always exist (so at the end it actualy check command).

[andychu]

OK the docs rendered now:

https://op.oilshell.org/uuu/github-jobs/8214/ovm-tarball.wwz/_release/VERSION/doc/error-catalog.html

---

I think the idioms for OSH and YSH will be very different here

obviously if you switch to YSH, then the script won't work under any other shell

But for OSH, there is an extremely large common subset with bash and POSIX shell

---

thanks for reporting the missing location!

[ale5000-git]

obviously if you switch to YSH, then the script won't work under any other shell

I will try make at least a part of the script work on both; the script is already tested on more than 10 shells so it doesn't use much advanced features.