oguz-ismail2

This is one of those places where Bash diverges from POSIX. The standard says `echo &>/dev/null' is two commands, namely `echo &' and `>/dev/null', but Bash interprets it as redirect both stdout and stderr of `echo' to `/dev/null' both in normal and POSIX mode.

Nit pick, but

>FILE* f = fopen(path, "rb");

>...

>if (fseek(f, 0, SEEK_END) != 0) return option_charp_none();

>long len = ftell(f);

does ISO C guarantee this'll work these days? How come there's no fread+realloc fallback?

It's a question of scale. Neither crime is less serious but far more children are groomed and abused over Discord than flown in via some super rich sicko's private jet for a 'costume party'.

What sibling comment says. Bash does suppress nonexistent products when the pattern includes a glob metacharacter and `shopt -s nullglob' is in effect, but I didn't see a flag or anything to achieve that in the project README.

Since when `{...}' syntax is a glob pattern? What does `{a,b}/c' produce when there is no directory named `a'?

Title says Unix, renameat2 is Linux-only.

> The Ashley Book of Knots is fantastic.

Yup. Referring to knots by their ABoK numbers is also more practical than by their wildly varying names.

fish and zsh real silent since this dropped

> How does that work, with syscalls being unable to be called except from the system’s libc?

OpenBSD allows system calls being made from shared libraries whose names start with `libc.so.' and all static binaries, as long as they include an `openbsd.syscalls' section listing call sites.

*horses

Does this spawn a new shell for every instance of $`...`?

>uuidgen

That's neither a standard CLI utility nor a bash builtin.

How is any of that a subtle difference between platforms?