Re: [PATCH 2/2] html-device-smoke-test.sh: Use printf(1) portably.

2025-04-11 Thread G. Branden Robinson
At 2025-04-11T06:26:19-0500, G. Branden Robinson wrote: > -printf "\('a" | "$groff" -C -k -Thtml | grep -qx 'á' \ > +printf '\('a | "$groff" -C -k -Thtml | grep -qx 'á' \ > || wail Sorry, I botched that. My rebase wasn't where I thought it was when I tested. This should work better. -print

Re: [PATCH 2/2] html-device-smoke-test.sh: Use printf(1) portably.

2025-04-11 Thread G. Branden Robinson
At 2025-03-30T22:24:18+, Lennart Jablonka wrote: > POSIX doesn’t explicitly specify (or explicitly un-specify) what > happens when a backslash in the format string is followed by a > character other than those listed by POSIX with special behavior. > OpenBSD’s printf, at least, warns about it a

[PATCH 2/2] html-device-smoke-test.sh: Use printf(1) portably.

2025-03-30 Thread Lennart Jablonka
POSIX doesn’t explicitly specify (or explicitly un-specify) what happens when a backslash in the format string is followed by a character other than those listed by POSIX with special behavior. OpenBSD’s printf, at least, warns about it and prints the literal character following the backslash. Th