GNU bug report logs - #74502
grep.in.1: Some remarks about this man page

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 74502 in the body.
You can then email your comments to 74502 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bjarni Ingi Gislason <bjarniig <at> simnet.is>
To: bug-grep <at> gnu.org
Subject: grep.in.1: Some remarks about this man page
Date: Sun, 24 Nov 2024 01:06:23 +0000

[Message part 1 (text/plain, inline)]

Package: grep
Version: upstream
Severity: minor

  Following comes from the next version of "groff" (> 1.23.0).

   * What led up to the situation?

     Checking for defects with

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page"

  [Use "groff -e ' $' <file>" to find trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?


troff: backtrace: file '<stdin>':14
troff:<stdin>:14: error: character '|' is not allowed as a delimiter
troff: backtrace: file '<stdin>':15
troff:<stdin>:15: warning: missing closing delimiter in output comparison operator; expected a special character, got a newline
troff: backtrace: file '<stdin>':27
troff:<stdin>:27: error: character '|' is not allowed as a delimiter
troff: backtrace: file '<stdin>':27
troff:<stdin>:27: warning: expected numeric expression, got a space


   * What outcome did you expect instead?

     No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.

[chk_man.err.grep.in.1 (text/plain, attachment)]

Message #8 received at 74502 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Bjarni Ingi Gislason <bjarniig <at> simnet.is>
Cc: 74502 <at> debbugs.gnu.org
Subject: Re: bug#74502: grep.in.1: Some remarks about this man page
Date: Sat, 23 Nov 2024 18:17:39 -0800

Thanks, but that's a recently-introduced groff bug. I reported it here:

https://savannah.gnu.org/bugs/index.php?66481

Message #13 received at 74502-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Bjarni Ingi Gislason <bjarniig <at> simnet.is>
Cc: 74502-done <at> debbugs.gnu.org
Subject: Re: bug#74502: grep.in.1: Some remarks about this man page
Date: Fri, 21 Mar 2025 13:25:34 -0700

[Message part 1 (text/plain, inline)]

On 11/23/24 18:17, Paul Eggert wrote:
> that's a recently-introduced groff bug. I reported it here:
> 
> https://savannah.gnu.org/bugs/index.php?66481

From the followup to that groff bug report, it appears that the groff 
maintainers don't consider this to be a bug, though they do say it is a 
compatibility issue. To work around this for grep, I installed the first 
attached patch. I noticed some other glitches too (some with traditional 
troff) and installed the second attached patch while I was in the 
neighborhood.

Closing the bug report. Thanks again for reporting the issue.

[0001-doc-use-w-.-not-w.patch (text/x-patch, attachment)]

[0002-doc-update-man-for-groff-1.23.0-and-apostrophes.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.