Hi Branden,
On 8/23/22 00:08, G. Branden Robinson wrote:
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 functions.
Maybe I'm having a senior moment but I don'
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 functions.
Maybe I'm having a senior moment but I don't get what this has to do
with groff? groff rolls its own
On Sunday, 21 August 2022 17:26:55 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2022-08-21T01:12:07+0100, Deri wrote:
> > Gropdf is different, it takes into account all download files found,
> > so there is no need to duplicate entries into the site-font download
> > file. You could organise y
Hi Ralph,
On 8/22/22 10:17, Ralph Corderoy wrote:
Hi Alejandro,
I fear that I might be making one of those structure definitions go
past the right margin, and there are so many, that it's not funny
rendering all of them to check
No, it's clearly a job for a machine.
$ cat longline.man
.TH
Hi Ralph, Branden,
On 8/22/22 10:04, Ralph Corderoy wrote:
Hi Branden,
(B) I see a deviation from the GNU Coding Standards for diagnostic
messages; we don't need a space after "troff:" when it's followed
by a file name.
It seems much of the word doesn't comply
$ sed -f /etc/p
Hi Alejandro,
> I fear that I might be making one of those structure definitions go
> past the right margin, and there are so many, that it's not funny
> rendering all of them to check
No, it's clearly a job for a machine.
> $ cat longline.man
> .TH a b c d
> .SH foo
> .nf
> this is a very long
Hi Branden,
> (B) I see a deviation from the GNU Coding Standards for diagnostic
> messages; we don't need a space after "troff:" when it's followed
> by a file name.
It seems much of the word doesn't comply
$ sed -f /etc/passwd
sed: file /etc/passwd line 3: extra characters afte
