GNU bug report logs - #75582
GNU grep 3.4 — enhancing manual

Previous Next

Package: grep;

Reported by: Anton Samokat <samokat700 <at> gmail.com>

Date: Wed, 15 Jan 2025 14:37:03 UTC

Severity: normal

Done: Jim Meyering <jim <at> meyering.net>

Bug is archived. No further changes may be made.

Full log

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

From: "David G. Pickett" <dgpickett <at> aol.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: "75582-done <at> debbugs.gnu.org" <75582-done <at> debbugs.gnu.org>,
 sur-behoffski <sur-behoffski <at> grouse.com.au>,
 "jackson <at> fastmail.fm" <jackson <at> fastmail.fm>
Subject: Re: bug#75582: GNU grep 3.4 — enhancing manual
Date: Sat, 18 Jan 2025 17:35:10 +0000 (UTC)

[Message part 1 (text/plain, inline)]
 No -r activity?
    On Saturday, January 18, 2025 at 12:30:01 AM EST, Jim Meyering <jim <at> meyering.net> wrote:   

 On Fri, Jan 17, 2025 at 10:35 AM David G. Pickett <dgpickett <at> aol.com> wrote:
> Should both -r and file names raise an error?
>
> $ grep -r xxx yyy zzz
> grep: yyy: No such file or directory
> grep: zzz: No such file or directory

That is expected behavior.
In that case, you've made a legitimate request to search recursively
for "xxx" in yyy and zzz.
It would probably elicit no diagnostic if you had files or directories
named yyy and zzz.
  
[Message part 2 (text/html, inline)]
This bug report was last modified 184 days ago.

Previous Next

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