From: Richard Stallman <rms@gnu.org>
Cc: drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Highlighting in grep buffer
Date: Sun, 11 Apr 2004 23:52:42 -0400 [thread overview]
Message-ID: <E1BCsV0-0007ee-V2@fencepost.gnu.org> (raw)
In-Reply-To: <873c7be197.fsf@mail.jurta.org> (message from Juri Linkov on Sun, 11 Apr 2004 01:28:08 +0300)
> It needs comments to explain what GREP_COLOR means
> and what that value means and why.
According to grep man page, the environment variable GREP_COLOR
specifies the marker for highlighting, GREP_OPTIONS specifies default
options to be placed in front of any explicit options, and the option
--color surrounds the matching string with the marker found in GREP_COLOR
environment variable.
Ok, please add comments in the Lisp code with that information.
Don't expect people maintaining Emacs to know such obscure
things about GNU grep!
> It may be less reliable, in that it may not work with non-GNU grep
> programs. Perhaps that is ok; people should install GNU grep.
Even though this feature will not be available for non-GNU greps,
I can't tell if the GREP_OPTIONS=--colors will cause them to fail.
It could be they will simply not notice. Could you arrange to test
this on a few recent modern?
next prev parent reply other threads:[~2004-04-12 3:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 22:03 Highlighting in grep buffer Richard Stallman
2004-04-05 23:05 ` Drew Adams
2004-04-07 17:45 ` Richard Stallman
2004-04-07 18:16 ` Drew Adams
2004-04-08 4:21 ` Juri Linkov
2004-04-08 16:38 ` Stefan Monnier
2004-04-10 22:29 ` Juri Linkov
2004-04-11 23:20 ` Stefan Monnier
2004-05-06 8:55 ` Juri Linkov
2004-05-06 14:39 ` Stefan Monnier
2004-05-06 21:03 ` Miles Bader
2004-05-08 21:46 ` Juri Linkov
2004-04-09 22:46 ` Richard Stallman
2004-04-10 22:28 ` Juri Linkov
2004-04-12 3:52 ` Richard Stallman [this message]
2004-04-12 4:32 ` Miles Bader
[not found] <DNEMKBNJBGPAOPIJOOICMEGCCAAA.drew.adams@oracle.com>
2004-04-13 11:45 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1BCsV0-0007ee-V2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).