On Sun, Feb 25, 2007 at 12:37:52AM -0500, Kamaraju Kusumanchi wrote:
> >if [ ! -z "$PS1" ]; then
> > function grep(){ command grep --color=always "$@"; }
> >fi
>
> Adding these 3 lines to .bashrc fixed the problem. Nice workaround.
It's less of a workaround and more The Right Thing To Do :-)
On Wed, Dec 27, 2006 at 05:27:19PM -0500, Kamaraju Kusumanchi wrote:
> Package: devscripts
> Version: 2.9.26
> Followup-For: Bug #404635
>
> A little more debugging, I found that the culprit is either of GREP_OPTIONS,
> GREP_COLOR environment variables. Both these options are documented in the man
clone 404635 -1
reassign -1 grep
retitle -1 grep: GREP_OPTIONS allows a user to break unrelated shell scripts
thanks
To the grep maintainer: please see the BTS entry for this bug:
essentially, by using an invasive setting for GREP_OPTIONS, grep now
breaks for this user when it is used in shell scr
tags 404635 + patch
thanks
Hi,
On Thu, 2006-12-28 at 12:53 +, Julian Gilbey wrote:
> On Wed, Dec 27, 2006 at 05:27:19PM -0500, Kamaraju Kusumanchi wrote:
> > A little more debugging, I found that the culprit is either of GREP_OPTIONS,
> > GREP_COLOR environment variables. Both these options a
On Wed, Dec 27, 2006 at 05:27:19PM -0500, Kamaraju Kusumanchi wrote:
> Package: devscripts
> Version: 2.9.26
> Followup-For: Bug #404635
>
> A little more debugging, I found that the culprit is either of GREP_OPTIONS,
> GREP_COLOR environment variables. Both these options are documented in the man
Package: devscripts
Version: 2.9.26
Followup-For: Bug #404635
A little more debugging, I found that the culprit is either of GREP_OPTIONS,
GREP_COLOR environment variables. Both these options are documented in the man
page of grep. On my machine I have
$echo $GREP_OPTIONS
--color=always
$echo $G
6 matches
Mail list logo
