GNU bug report logs - #27763
egrep.sh: grep missing path

Previous Next

Package: grep;

Reported by: Santiago Ruano Rincón <santiagorr <at> riseup.net>

Date: Wed, 19 Jul 2017 07:24:02 UTC

Severity: normal

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

Bug is archived. No further changes may be made.

Full log

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

From: Santiago Ruano Rincón <santiagorr <at> riseup.net>
To: 27763 <at> debbugs.gnu.org, 863002 <at> bugs.debian.org
Subject: Re: bug#27763: egrep.sh: grep missing path
Date: Wed, 19 Jul 2017 14:05:54 +0200

El 19/07/17 a las 02:56, Paul Eggert escribió:
> Santiago Ruano Rincón wrote:
> 
> > As suggested by this user, it would be better if egrep/fgrep script
> > calls grep using its absolute path.
> 
> Debian bug 863002 doesn't explain why it would be better, as the original
> bug report is evidently a case of misunderstanding how PATH works.

The bug submitter sent me I private mail about that. I let him explain
it publicly answering to this mail.
For me, "it would be better" just because it makes egrep/fgrep call the
grep installed by the package. 

> Although we used to do it the way you're suggesting, the current way is
> better for users who want to specify their own 'grep' command with their own
> option preferences, and to have these preferences also apply to 'egrep' and
> 'fgrep'. See:
> 
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19998

That makes sense.

Thanks for your answer,

Santiago
This bug report was last modified 5 years and 140 days ago.

Previous Next

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