bug#31705: closed (five grep / egrep issues)

[GNU bug Tracking System]

Your message dated Tue, 31 Dec 2019 23:44:26 -0800
with message-id <address@hidden>
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
address@hidden.)


-- 
31705: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31705
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: five grep / egrep issues Date: Sun, 3 Jun 2018 20:48:31 -0700

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

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#31705: five grep / egrep issues
>
>
>
>
> Date: 
>
> Tue, 31 Dec 2019 23:44:26 -0800
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
>
>
>
>
> No further comment for over a year, so closing the bug report.
>
>
> --- End Message ---