GNU bug report logs -
#15127
grep not taking last conflicting option as choice?
Previous Next
Reported by: Linda Walsh <coreutils <at> tlinx.org>
Date: Mon, 19 Aug 2013 02:52:01 UTC
Severity: normal
Tags: notabug
Done: Eric Blake <eblake <at> redhat.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#15127: grep not taking last conflicting option as choice?
which was filed against the coreutils package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 15127 <at> debbugs.gnu.org.
--
15127: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15127
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
tag 15127 notabug
thanks
On 08/18/2013 08:50 PM, Linda Walsh wrote:
>
> Isn't it usually the case with conflicting options that the last
> one gets taken as the choice, with choices on the command line
> overriding choices in the environment?
>
> Grep doesn't seem to follow this convention.
>
> Is there a reason why grep doesn't or did it
> used to and now chooses to do nothing in the case of
> conflicting options? (eg. -P v. -E)
>
> I think the earlier behavior, especially in respect
> to cmdline value overriding the environment is more
> useful otherwise lines built up both by successive passes
> in make files and with those who specify defaults in GREP_OPTIONS,
> but expect cmd-line usage to override ENV...
>
> (coreutils 8.21)
>
> (or is grep not part of coreutils these days...hmmm...)
Grep is its own project (bug-grep <at> gnu.org, per 'grep --help' output).
As such, I'm closing this as not a coreutils bug.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[signature.asc (application/pgp-signature, attachment)]
[Message part 5 (message/rfc822, inline)]
Isn't it usually the case with conflicting options that the last
one gets taken as the choice, with choices on the command line
overriding choices in the environment?
Grep doesn't seem to follow this convention.
Is there a reason why grep doesn't or did it
used to and now chooses to do nothing in the case of
conflicting options? (eg. -P v. -E)
I think the earlier behavior, especially in respect
to cmdline value overriding the environment is more
useful otherwise lines built up both by successive passes
in make files and with those who specify defaults in GREP_OPTIONS,
but expect cmd-line usage to override ENV...
(coreutils 8.21)
(or is grep not part of coreutils these days...hmmm...)
This bug report was last modified 11 years and 275 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.