[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Split diagnostic about blank lines in input
From: |
G. Branden Robinson |
Subject: |
Re: Split diagnostic about blank lines in input |
Date: |
Tue, 2 May 2023 10:17:03 -0500 |
Hi Alex,
At 2023-04-28T15:10:08+0200, Alejandro Colomar wrote:
> I've got some wish, which ISTR I already expressed at some point in
> the past. There's this diagnostic:
>
> an.tmac:man3/nxt_unit_init.3:62: style: blank line in input
>
> The thing is, for example C programs I do need to violate that. But,
> other than that, I want to see the diagnostic, if someone used it
> outside of an example.
>
> How about splitting this diagnostic, making two different diagnostics?
>
> style: blank line in input out of a EX/EE region
> style: blank line in input in a EX/EE region
>
> I would be able to grep out the second warning.
I have a counter-proposal. ;-)
How about adopting the use of a leading dummy character in otherwise
blank lines inside an `EX`/`EE` region?
Here's an example from sprof(1).
Before:
.EX
$ \fBcat prog.c\fP
#include <stdlib.h>
void x1(void);
void x2(void);
int
main(int argc, char *argv[])
{
x1();
x2();
exit(EXIT_SUCCESS);
}
.EE
After:
.EX
$ \fBcat prog.c\fP
#include <stdlib.h>
\&
void x1(void);
void x2(void);
\&
int
main(int argc, char *argv[])
{
x1();
x2();
exit(EXIT_SUCCESS);
}
.EE
Regards,
Branden
signature.asc
Description: PGP signature
- Re: Split diagnostic about blank lines in input,
G. Branden Robinson <=