GNU bug report logs - #29354
GREP_OPTIONS not processed

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#29354: closed (GREP_OPTIONS not processed)
Date: Tue, 31 Dec 2019 20:03:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 31 Dec 2019 12:02:34 -0800
with message-id <d9a52e5a-6c9c-5fb5-02ce-70b806dc0d9e <at> cs.ucla.edu>
and subject line Re: GREP_OPTIONS not processed
has caused the debbugs.gnu.org bug report #29354,
regarding GREP_OPTIONS not processed
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
29354: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29354
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Dennis <grep+user <at> mgssub.com>
To: Grep Bugs <bug-grep <at> gnu.org>
Subject: GREP_OPTIONS not processed
Date: Sat, 18 Nov 2017 17:55:47 -0600

Running grep 2.20 on Debian Jessie.

Apparently grep is not processing the GREP_OPTIONS
environment variable. I have been setting the "-i" option in
there for years as that is the most useful for me. Lately it
has not been working. I have done many tests and it seems
that GREP_OPTIONS is completely ignored.

[Message part 3 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Dennis <grep+user <at> mgssub.com>
Cc: "Santiago R.R." <santiagorr <at> riseup.net>, 29354-done <at> debbugs.gnu.org
Subject: Re: GREP_OPTIONS not processed
Date: Tue, 31 Dec 2019 12:02:34 -0800

No further comment on this bug report for two years, and I still cannot
reproduce it. Closing the bug report.

Previous Next

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