pcre2grep.1 - fix warning about undefined macro 0 #673
Conversation
Debian's "lintian" picked this up - line 950 in the man page starts with a ' which is how you start a roff request. You can reproduce the warning thus: ``` LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ man --warnings -E UTF-8 -l -Tutf8 -Z doc/pcre2grep.1 >/dev/null ``` The fix is to add a zero-width space (`\&`) to the start of the relevant line (indeed `groff_man(7)` suggests exactly this use for \&). Signed-off-by: Matthew Vernon <[email protected]>
\& is a zero-width space, which is occasionally useful. Signed-off-by: Matthew Vernon <[email protected]>
|
Arrgh, roff and groff madness. Thank you Matthew. Unfortunately, we have some Perl scripts which we use to process the man pages (which are the "source of truth") and the Perl scripts are strict at enforcing a known subset of the nroff dialect.
We can definitely get this into 10.45. |
|
I've pushed a commit which causes CheckMan to be happy with We could change the line-wrapping, but I worry that future-us will come along and change it back again in the future... |
|
Hmm, I expect the I'll do that later this morning. |
Signed-off-by: Matthew Vernon <[email protected]>
|
I think I've done that one too (I ran it locally, and the output looked plausible) |
|
Great, thank you again Matthew! The check I added will prevent this recurring in future. |
Debian's "lintian" picked this up - line 950 in the man page starts with a ' which is how you start a roff request. You can reproduce the warning thus: ``` LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ man --warnings -E UTF-8 -l -Tutf8 -Z doc/pcre2grep.1 >/dev/null ``` The fix is to add a zero-width space (`\&`) to the start of the relevant line (indeed `groff_man(7)` suggests exactly this use for \&). --------- Co-authored-by: Matthew Vernon <[email protected]>
Debian's "lintian" picked this up - line 950 in the man page starts with a
'which is how you start a roff request. You can reproduce the warning thus:The fix is to add a zero-width space (
\&) to the start of the relevant line (indeedgroff_man(7)suggests exactly this use for\&).This is obviously not a critical issue, but it'd be nice if it made it into 10.45 please :)