Bug 602867 - config file to disable colors
config file to disable colors
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: grep (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Jaroslav Škarvada
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-10 18:05 EDT by Zing
Modified: 2010-06-11 05:42 EDT (History)
2 users (show)

See Also:
Fixed In Version: grep-2.6.3-4.fc14
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-11 05:42:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
/etc/GREP_COLORS (94 bytes, text/plain)
2010-06-10 18:05 EDT, Zing
no flags Details
colorgrep.sh patch (378 bytes, patch)
2010-06-10 18:06 EDT, Zing
no flags Details | Diff
colorgrep.csh patch (478 bytes, patch)
2010-06-10 18:07 EDT, Zing
no flags Details | Diff

  None (edit)
Description Zing 2010-06-10 18:05:08 EDT
Description of problem:
We need a way to globally disable colors now that the default is colors.

I've added an /etc/GREP_COLORS file that accepts a "COLOR none" stanza, and extended the profile scripts to check it.

Version-Release number of selected component (if applicable):
grep-2.6.3-3.fc14.x86_64.rpm

Additional info:
Feel free to implement this in another way.  I just need a way to disable this globally.  I loosely followed DIR_COLORS and the colorls scripts.
Comment 1 Zing 2010-06-10 18:05:49 EDT
Created attachment 423069 [details]
/etc/GREP_COLORS
Comment 2 Zing 2010-06-10 18:06:44 EDT
Created attachment 423070 [details]
colorgrep.sh patch
Comment 3 Zing 2010-06-10 18:07:17 EDT
Created attachment 423071 [details]
colorgrep.csh patch
Comment 4 Jaroslav Škarvada 2010-06-11 03:08:26 EDT
Thanks, that's similar to LS, I will integrate it.
Comment 5 Jaroslav Škarvada 2010-06-11 05:42:09 EDT
Fixed in grep-2.6.3-4.fc14.

Note You need to log in before you can comment on or make changes to this bug.