groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Split diagnostic about blank lines in input


From: Alejandro Colomar
Subject: Re: Split diagnostic about blank lines in input
Date: Wed, 3 May 2023 00:23:44 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0

Hi Branden,

On 5/2/23 17:17, G. Branden Robinson wrote:
> 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?

Sounds reasonable.  Not too invasive.

Thanks,
Alex

> 
> 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

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]