GNU bug report logs - #23590
25.0.94; Errors in default lgrep command

Previous Next

Package: emacs;

Reported by: Alex <agrambot <at> gmail.com>

Date: Sat, 21 May 2016 00:12:01 UTC

Severity: normal

Tags: fixed, patch

Found in version 25.0.94

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alex <agrambot <at> gmail.com>
Cc: john.b.mastro <at> gmail.com, 23590 <at> debbugs.gnu.org
Subject: Re: bug#23590: 25.0.94; Errors in default lgrep command
Date: Sat, 23 Jul 2016 21:00:37 +0300

> From: Alex <agrambot <at> gmail.com>
> Cc: John Mastro <john.b.mastro <at> gmail.com>,  23590 <at> debbugs.gnu.org
> Date: Sat, 23 Jul 2016 11:28:21 -0600
> 
> > Yes, but I don't understand why the OP says these are errors.  They
> > aren't; they are just informative messages from Grep.
> 
> When I use lgrep I already know that I'm not going to be searching
> directories. I find such messages to be useless clutter.

They cannot be avoided portably.  Sorry.

> Additionally, while zsh doesn't error on this part (with the workarounds
> that John provided), bash does appear to error because it is including
> directories:
> 
> Grep exited abnormally with code 2 at ...

Because of this:

> grep: ..?*: No such file or directory
This bug report was last modified 4 years and 299 days ago.

Previous Next

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