Control: tag -1 fixed-upstream I beg you to make your bug reports less insanely verbose. It takes me considerable time to wade through all the boilerplate to find the bits that are actually relevant!
On Thu, Feb 13, 2025 at 10:38:47AM +0000, Bjarni Ingi Gislason wrote: > Output from "test-groff -mandoc -t -ww -z manpath.5": (shortened list) > > 1 Use macro '.I' for one argument or split argument. > 1 .IR is for at least 2 arguments, got 1 Fixed. > Strings longer than 3/4 of a standard line length (80) > Use "\:" to split the string at the end of an output line, for example a > long URLs (web address) > > 72 .IR > /usr/share/man/newOS:/usr/share/man:/usr/local/man/newOS:/usr/local/man . Reasonable suggestion. Applied. > Add a comma (or \&) after "e.g." and "i.e.", or use English words > (man-pages(7)). The advice to use a comma after "e.g." is specific to US English. As a speaker of UK English, I see no reason to follow this prescription. However, I've added "\&". > Put a parenthetical sentence, phrase on a separate line, > if not part of a code. > See man-pages(7), item "semantic newline". > > manpath.5:203:If a particular extension is not in this list (say, 1mh) it > will be > manpath.5:217:cat pages will not be created (if missing) or displayed. > manpath.5:223:cat pages will not be created (if missing) or displayed. That seems excessively fussy for such short parentheses, as opposed to long parentheses that contain whole clauses. I haven't applied this. > Remove quotes when there is a printable > but no space character between them > and the quotes are not for emphasis (markup), > for example as an argument to a macro. > > 13:.TH MANPATH 5 "2024-08-29" "2.13.0" "/etc/manpath.config" The quotes are harmless, and given that what's inside them is substituted at build time, I prefer to keep them. https://gitlab.com/man-db/man-db/-/commit/2607d203472efb036d888e9e7997724a41a53876 Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
