From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] 'if echo hello' in .bashrc
Date: Fri, 8 May 2009 14:38:58 +0100 [thread overview]
Message-ID: <742F0C43-196E-465B-9991-3DFF1C655803@stellar.eclipse.co.uk> (raw)
Hi there,
I've just realised that grep hasn't been highlighting results in
colour, and it occurred to me that I was sure it has supported this
facility for some time. Thus I discovered the --colour=always flag to
grep and trying to make this permanent I stumbled upon this site: http://www.ccs.neu.edu/home/katz/unix-colors.html
To find the part to which I refer you'll need to scroll down about
halfway through that page to "Colorize grep"; the author advises adding:
if echo hello|grep --color=auto l >/dev/null 2>&1; then
export GREP_OPTIONS='--color=auto' GREP_COLOR='1;32'
fi
to ~/.bashrc
Why does he echo hello, please? Is this to ensure that the file is
not sourced by a non-interactive shell, or by a script or something? I
understood that that was the difference between .bashrc
& .bash_profile, anyway - that "interactive commands" like colourising
stuff should go in .bashrc, to use /usr/local/mount instead of the
system on then one might alias that in .bash_profile.
It's early in the morning here, so obviously I'm not getting something.
Thanks in advance for any pointers,
Stroller.
next reply other threads:[~2009-05-08 13:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 13:38 Stroller [this message]
2009-05-08 14:01 ` [gentoo-user] 'if echo hello' in .bashrc Mike Kazantsev
2009-05-08 14:09 ` Stroller
2009-05-08 14:10 ` Alan McKinnon
2009-05-08 14:38 ` Christian
2009-05-08 14:43 ` Alan McKinnon
2009-05-08 14:57 ` Eray Aslan
2009-05-08 14:59 ` Etaoin Shrdlu
2009-05-08 14:51 ` Alan McKinnon
2009-05-08 15:13 ` Etaoin Shrdlu
2009-05-08 16:22 ` Carlos Hendson
2009-05-08 18:08 ` James Rowe
2009-05-08 18:05 ` Mike Kazantsev
2009-05-09 10:15 ` Stroller
2009-05-09 10:41 ` Etaoin Shrdlu
2009-05-09 10:43 ` Stroller
2009-05-09 11:13 ` Etaoin Shrdlu
2009-05-09 14:38 ` Joerg Schilling
2009-05-09 11:38 ` Mike Kazantsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=742F0C43-196E-465B-9991-3DFF1C655803@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox