Hi Alex,
At 2023-05-07T20:13:54+0200, Alejandro Colomar wrote:
> On 5/7/23 04:20, G. Branden Robinson wrote:
> > I'm following the GNU Coding Standards here.
> >
> > https://www.gnu.org/prep/standards/standards.html#Errors
>
> Oh yeah, those. I guess I can't argue much against that practice
> t
On 5/7/23 04:20, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2023-05-03T01:26:55+0200, Alejandro Colomar wrote:
>>> troff:man3/unlocked_stdio.3:123: warning [p 2, 1.8i, div '3tbd1,0', 0.3i]:
>>> cannot break line
>>>
>>> an.tmac:man4/cciss.4:164: style: blank line in input
>>>
>>> man4/console
Hi Alex,
At 2023-05-03T01:26:55+0200, Alejandro Colomar wrote:
> > troff:man3/unlocked_stdio.3:123: warning [p 2, 1.8i, div '3tbd1,0', 0.3i]:
> > cannot break line
> >
> > an.tmac:man4/cciss.4:164: style: blank line in input
> >
> > man4/console_codes.4:324: warning: table wider than line lengt
Hi Alejandro,
Alejandro Colomar wrote on Wed, May 03, 2023 at 01:26:55AM +0200:
> I find it more readable when there's one space between the program
> that generates the warning and the file. That's what mandoc(1) does,
> and in general, what any program that relies on perror(3) does (I'm
> assu
Hi Branden,
On 5/3/23 00:21, Alejandro Colomar wrote:
>
> troff:man3/unlocked_stdio.3:123: warning [p 2, 1.8i, div '3tbd1,0', 0.3i]:
> cannot break line
>
> an.tmac:man4/cciss.4:164: style: blank line in input
>
> man4/console_codes.4:324: warning: table wider than line length minus
> indenta
