Mingye Wang

Oh no, the getpwnam_r error handling is also incomplete per man page. Well it does catch all possible errors; it's just there is a wasted error code.

Unfunny aside: gcc somehow emits 2 strlen calls on home_dir. Dumbass!

eh don't write this into any documentation without crediting the .sh part! bsd-3-clause is compatible with gpl though.

FORTIFY_SOURCE is surprisingly widespread. [macOS libc](https://github.com/apple-open-source-mirror/Libc/tree/macos-10145/secure) have their independently implemented functions. So does the [mingw-w64 libc](https://github.com/mirror/mingw-w64/tree/c9fcb18/mingw-w64-crt/ssp). On other systems, the gcc "libssp", which is independent of the libc, can also...

My terrible, terrible idea is that we do both `transl_except` and table expansion. The former would be used for cases when the recoding is definitively known, the latter for messing...

Another helpful thing to have is to symlink GNU things to a `g` prefix in other systems like `osx`, e.g. ` osx/gxargs -> linux/xargs`. This is how many systems like...

The other good thing about symlinks for this issue is that we can be a bit more pedantic and start referring things to the names of where they came from...

Likely unrelated, but your environment has an encoding issue: `‘simde_vext_p64’` indicates that you have UTF-8 output from gcc (presumably a remote machine with `LC_ALL=something.UTF-8`), but your terminal program is decoding...

Hmmmm.... let me check my old email link to see what I considered back then. Okay, I'm mostly back on track. Regarding `sh -c` + positional: currently this stuff is...

Bash is a bad idea too, because Cygwin/MSYS2 argument parsing is not what nodejs/uvlib expects. Try to coax `echo.exe` from MSYS into printing out `C:\"` from outside of Cygwin/MSYS2 and...