From: Juri Linkov <juri@jurta.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [jidanni@jidanni.org: Re: find-grep makes raw terminal ANSI]
Date: Sun, 18 Nov 2007 01:59:17 +0200 [thread overview]
Message-ID: <87abpc4dgm.fsf@jurta.org> (raw)
In-Reply-To: <E1ItX7V-0007j9-Sa@fencepost.gnu.org> (Richard Stallman's message of "Sat, 17 Nov 2007 18:30:37 -0500")
> > He is arguing that setting GREP_COLOR is a mistake
>
> GREP_COLOR is for compatibility with older grep versions.
> grep.el also uses GREP_COLORS for newer versions.
> So everything in this regard is already correct in grep.el.
>
> I think we are miscommunicating. The problem he's talking about
> is that this affects grep even if grep is piped to another command,
> and that gives bad results (sometimes).
>
> I expect that the problem is the same regardless of precisely which
> envvar is used. Is that not so?
Yes, the problem is the same for the deprecated envvar GREP_COLOR and
a newer envvar GREP_COLORS. I understood that part of the complaint was
using the deprecated envvar GREP_COLOR instead of newer GREP_COLORS.
Since Emacs sets both there is no problem for supporting old and new
versions of GNU grep.
As for the main problem, Stefan suggested a workable solution.
--
Juri Linkov
http://www.jurta.org/emacs/
prev parent reply other threads:[~2007-11-17 23:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 4:29 [jidanni@jidanni.org: Re: find-grep makes raw terminal ANSI] Richard Stallman
2007-11-16 21:54 ` Juri Linkov
2007-11-17 4:24 ` Stefan Monnier
2007-11-17 15:32 ` Juri Linkov
2007-11-17 17:28 ` Drew Adams
2007-11-17 22:50 ` Eli Zaretskii
2007-11-17 23:04 ` Drew Adams
2007-11-18 0:29 ` David Kastrup
2007-11-18 4:14 ` Eli Zaretskii
2007-11-17 22:54 ` Juri Linkov
2007-11-18 3:18 ` Stefan Monnier
2007-11-18 10:45 ` Andreas Schwab
2007-11-18 12:05 ` Juri Linkov
2007-11-19 16:00 ` Stefan Monnier
2007-11-18 22:45 ` Richard Stallman
2007-11-17 23:30 ` Richard Stallman
2007-11-17 23:59 ` Juri Linkov [this message]
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=87abpc4dgm.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.