GNU bug report logs -
#62272
Erroneous claim in grep man page
Previous Next
Reported by: dakra137 <at> gmail.com
Date: Sun, 19 Mar 2023 12:47:01 UTC
Severity: normal
Done: Jim Meyering <jim <at> meyering.net>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 62272 in the body.
You can then email your comments to 62272 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-grep <at> gnu.org
:
bug#62272
; Package
grep
.
(Sun, 19 Mar 2023 12:47:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
dakra137 <at> gmail.com
:
New bug report received and forwarded. Copy sent to
bug-grep <at> gnu.org
.
(Sun, 19 Mar 2023 12:47:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
This is a request and further endorsement of a report from 2008, ending
with https://lists.gnu.org/archive/html/bug-grep/2008-08/msg00002.html
Request: Either add four words to the manpage or delete the entire
sentence.
ASIS: "In GNU grep there is no difference in available functionality
between basic and extended syntaxes."
TOBE: "Although the syntaxes differ, in GNU grep there is no difference in
available functionality between basic and extended syntaxes."
Reasoning: The user should not suffer for not realizing that "no difference
in available functionality" does not imply "no difference in syntax."
Example:
*$* *grep -i "([A-Z])\1\1" *
grep: Invalid back reference
#but no problem with:
*$* *grep -i -E "([A-Z])\1\1"*
or
*$* *grep -i "\([A-Z]\)\1\1" *
---
Thank you,
*David A. Kra*
__________________________________________________________________
[Message part 2 (text/html, inline)]
Reply sent
to
Jim Meyering <jim <at> meyering.net>
:
You have taken responsibility.
(Mon, 20 Mar 2023 01:55:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
dakra137 <at> gmail.com
:
bug acknowledged by developer.
(Mon, 20 Mar 2023 01:55:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 62272-done <at> debbugs.gnu.org (full text, mbox):
tags notabug 62272
stop
On Sun, Mar 19, 2023 at 5:47 AM David Kra <dakra137 <at> gmail.com> wrote:
> This is a request and further endorsement of a report from 2008, ending
> with https://lists.gnu.org/archive/html/bug-grep/2008-08/msg00002.html
>
> Request: Either add four words to the manpage or delete the entire
> sentence.
> ASIS: "In GNU grep there is no difference in available functionality
> between basic and extended syntaxes."
>
> TOBE: "Although the syntaxes differ, in GNU grep there is no difference in
> available functionality between basic and extended syntaxes."
>
> Reasoning: The user should not suffer for not realizing that "no difference
> in available functionality" does not imply "no difference in syntax."
Thanks, but that sentence already says there are two different
syntaxes: basic and extended.
Those are different names, which usually implies they denote different things.
So adding those four words at the beginning of the sentence would be
unnecessary and repetitive.
I'm marking this as done, but discussion may continue.
Information forwarded
to
bug-grep <at> gnu.org
:
bug#62272
; Package
grep
.
(Mon, 20 Mar 2023 07:31:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 62272 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2023-03-19 02:27, David Kra wrote:
> TOBE: "Although the syntaxes differ, in GNU grep there is no difference in
> available functionality between basic and extended syntaxes."
I'm not a fan of "syntaxes". Although it is a word in computer science
it grates in my ear because in linguistics "syntax" is a field of study
and there is only one syntax just as there is only one rhetoric and
there is only one logic.
Anyway (to get off my soapbox :-) there's a bigger problem in the next
sentence, which says, "In other implementations, basic regular
expressions are less powerful." That's not true for POSIX BREs, as they
have back-references, which POSIX EREs lack. (This is documented in the
GNU grep manual's "Problematic Expressions" section.) And I doubt
whether it's true that PCRE2 is a strict superset of EREs so we should
scale the wording back a bit there too.
I installed the attached doc patch, which I hope fixes these problems.
(It also fixes a couple of troff typos I noticed in the neighborhood.)
[0001-doc-clarify-BRE-vs-ERE-bug-62272.patch (text/x-patch, attachment)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 17 Apr 2023 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 26 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.