[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Coding Standards for progname:file:line. (Was: Font path issue)
From: |
G. Branden Robinson |
Subject: |
Re: GNU Coding Standards for progname:file:line. (Was: Font path issue) |
Date: |
Mon, 22 Aug 2022 17:08:06 -0500 |
Hi Alex,
At 2022-08-22T20:18:38+0200, Alejandro Colomar wrote:
> Also, I'd keep the space, even if only for being able to use standard
> tools like perror(3), or common tools like the <err.h> functions.
Maybe I'm having a senior moment but I don't get what this has to do
with groff? groff rolls its own diagnostic functions; the closest it
gets to anything like perror() is strerror().
Regards,
Branden
signature.asc
Description: PGP signature
- Font path issue, Peter Schaffter, 2022/08/19
- Re: Font path issue, Deri, 2022/08/20
- Re: Font path issue, Robert Goulding, 2022/08/21
- Re: Font path issue, G. Branden Robinson, 2022/08/21
- Re: Font path issue, Ralph Corderoy, 2022/08/21
- Re: Font path issue, G. Branden Robinson, 2022/08/21
- GNU Coding Standards for progname:file:line. (Was: Font path issue), Ralph Corderoy, 2022/08/22
- Re: GNU Coding Standards for progname:file:line. (Was: Font path issue), Alejandro Colomar, 2022/08/22
- Re: GNU Coding Standards for progname:file:line. (Was: Font path issue),
G. Branden Robinson <=
- Re: GNU Coding Standards for progname:file:line. (Was: Font path issue), Alejandro Colomar, 2022/08/22
- Re: Font path issue, Deri, 2022/08/22