GNU bug report logs - #26648
What's wrong w/this grep?

Previous Next

Package: grep;

Reported by: "L. A. Walsh" <gnu <at> tlinx.org>

Date: Tue, 25 Apr 2017 07:46:02 UTC

Severity: normal

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

Bug is archived. No further changes may be made.

Full log


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

From: Zev Weiss <zev <at> bewilderbeest.net>
To: "L. A. Walsh" <gnu <at> tlinx.org>
Cc: 26648 <at> debbugs.gnu.org
Subject: Re: bug#26648: What's wrong w/this grep?
Date: Tue, 25 Apr 2017 02:58:36 -0500
On Tue, Apr 25, 2017 at 02:45:14AM CDT, L. A. Walsh wrote:
>> /usr/bin/grep --color=auto -I -D skip -d skip -exclude-from=EX -P -r xrm
>/usr/bin/grep: xrm: No such file or directory
>> /usr/bin/grep --version
>/usr/bin/grep (GNU grep) 2.21.31-adf9
>
>How did 'xrm' become a file name?
>
>It happened after I added the "-exclude-from=EX -P -r"
>to an alias... but it happens when I use
>the binary directly (i.e. no alias).
>
>I was expecting 'xrm' to be a pattern that was searched
>for in the files starting at the current directory.
>
>"New" to me -- use of the -exclude-from option.
>Of note: EX contains:
>*.orig
>*.1
>*.1.in
>
>
>Ideas?  Doesn't seem like correct action...
>

Perhaps '--exclude-from' rather than '-exclude-from'?





This bug report was last modified 8 years and 30 days ago.

Previous Next


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