an invalid timezone or at least not the timezone being used. Sadly, grdc
has no easy way of telling. If only there were some API to tell.
Further with grdc, I'd really like it if the string being displayed were
not necessarily all of $TZ, but limited to up to the last characters
(the end of the time zone string being more interesting than the start),
for n on the order of 40.
Paul Janzen.
e files, and surely
one doesn't want one's general utilities to be pwned by possible bugs in
the time-handling code exploited with custom files created outside
/usr/share/zoneinfo. But it's still a touch irritating-should-be-fixable
that, because the pledge() has to be after initscr(),
My error from 1998. Your diff is correct.
Paul Janzen.
On Wed, 28 Apr 2021, trondd wrote:
> Looks like we picked up some extra loopty loops during an update from
> NetBSD back in 1998.
>
> I sanity checked against NetBSD to make sure this matches their
> source.
>
> Tim
e sentences in
question weren't even describing NUL-terminated strings, but pointing
out that the function in question would ensure the presence of a
terminating NUL...
I doubt changing things is worth the bother, but using
Amen.
Paul Janzen.
quot;a NUL-terminated string") but not after a verb (e.g., "string foo
is NUL terminated"), according to at least many style guides.
Paul Janzen.
