GNU bug report logs - #31705
five grep / egrep issues

Previous Next

Package: grep;

Reported by: Phillip Feldman <phillip.m.feldman <at> gmail.com>

Date: Mon, 4 Jun 2018 07:24:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#31705: closed (five grep / egrep issues)
Date: Wed, 01 Jan 2020 07:45:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Tue, 31 Dec 2019 23:44:26 -0800
with message-id <34e6f1e7-0d7b-e880-d23b-b1bebe4b5afa <at> cs.ucla.edu>
and subject line Re: bug#31705: five grep / egrep issues
has caused the debbugs.gnu.org bug report #31705,
regarding five grep / egrep issues
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
31705: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31705
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Phillip Feldman <phillip.m.feldman <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: five grep / egrep issues
Date: Sun, 3 Jun 2018 20:48:31 -0700
[Message part 3 (text/plain, inline)]
I would like to report the following unrelated issues:

(1) `grep --help` and `egrep --help` should report the version number.

(2) `egrep [abc]+ *.txt` works as expected, but if I try to do `egrep
^[abc]+ *.txt`, which anchors the pattern to the start of the line, I get
no results,
even though there are lines that match the pattern.

(3) Specifying a pattern for FILE seems to work just fine unless one does a
recursive search.

(4) If one attempts to do a recursive search and omits the starting
directory, it would be helpful if the default were the current working
directory. An
alternative would be to generate a warning or error message. Simply failing
to produce any results is a bad design.

(5) If one provides an invalid regex, e.g., something like '*xyz' (a regex
can't begin with '*'), one should get a fatal error (grep and egrep accept
such a
regex without complaint, and simply return no results).

Phillip M. Feldman
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Phillip Feldman <phillip.m.feldman <at> gmail.com>
Cc: 31705-done <at> debbugs.gnu.org
Subject: Re: bug#31705: five grep / egrep issues
Date: Tue, 31 Dec 2019 23:44:26 -0800
No further comment for over a year, so closing the bug report.


This bug report was last modified 5 years and 139 days ago.

Previous Next


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