[RFC] Various pages: Use consistent style for lists (.IP)

2022-10-24 Thread Alejandro Colomar
Reported-by: Mike Frysinger Cc: Signed-off-by: Alejandro Colomar --- Hi Mike, I started doing this change to have a consistent style for lists. I used a few commands to find issues, and to check that the fixes are correct (i.e., I don't introduce typos): $ grep -r '^.IP ' man* \ | sort \

Re: [groff] 27/33: eqn(1): Fix content and style nits.

2022-10-24 Thread Mike Bianchi
> It may be, but I don't think that outweighs users knowing to search for > ‘bugs’ when they want to see if the man page has that section on > encountering odd behaviour. Historically, BUGS were there to acknowledge actual failures that had not yet been addressed. Witneess: http://man.cat

Re: [groff] 27/33: eqn(1): Fix content and style nits.

2022-10-24 Thread Ralph Corderoy
Hi Branden, > I've introduced or retained "Limitations" (sub)sections in several > groff man pages; often I find it a better fit for discussion of issues > than the historically well-attested "Bugs". Against Ingo's advice I > tend not to use that section title. We have a bug tracker for bugs; >

Re: [groff] 27/33: eqn(1): Fix content and style nits.

2022-10-24 Thread Dave Kemper
On 10/22/22, G. Branden Robinson wrote: > "Limitations" seems like a > better characterization of features that are inessential but desirable > and not yet implemented, or which would require redesign of other parts > of the software system to realize. That all makes sense, and seems to argue for