From: geoff.bache@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: Weird stuff printed out by emacs rgrep
Date: Sun, 22 Mar 2009 12:55:56 -0700 (PDT) [thread overview]
Message-ID: <754129e2-cab7-43b2-aa97-d81fedc338f0@e35g2000yqc.googlegroups.com> (raw)
In-Reply-To: mailman.3789.1237749011.31690.help-gnu-emacs@gnu.org
On Mar 22, 8:08 pm, Eli Zaretskii <e...@gnu.org> wrote:
> > From: geoff.ba...@gmail.com
> > Date: Sun, 22 Mar 2009 11:23:00 -0700 (PDT)
>
> > On Mar 22, 12:01 am, Eli Zaretskii <e...@gnu.org> wrote:
> > > > From: geoff.ba...@gmail.com
> > > > Date: Sat, 21 Mar 2009 14:02:47 -0700 (PDT)
>
> > > > Emacs starts /bin/tcsh -c find ... | xargs grep ...
> > > > Crucially, it sets the environment variable GREP_OPTIONS=' --
> > > > color=always'
>
> > > The current development sources change that to --color=auto.
>
> > Great, that would also fix my problem.
>
> > Do you know if this fix is present in any stable releases of emacs 22
> > yet?
>
> No, it was done only recently, in preparation for Emacs 23.
>
> But you can, of course, make the change in grep.el yourself, then
> recompile it, and be done.
I can happily do that at home (where I can also just reset
GREP_OPTIONS at the top of the offending SGE script), but not really
at work which has the same issue. I have no control over the emacs
installation and don't really want to start building and supporting my
own personal emacs there.
Is there any chance of a backport into emacs 22 or is that not being
patched any more? I believe I have more chance of convincing my
sysadmins to install an official emacs release than to start hacking
in elisp code :)
Geoff
next prev parent reply other threads:[~2009-03-22 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3609.1237522114.31690.help-gnu-emacs@gnu.org>
2009-03-21 21:02 ` Weird stuff printed out by emacs rgrep geoff.bache
2009-03-21 22:32 ` Drew Adams
2009-03-21 23:01 ` Eli Zaretskii
[not found] ` <mailman.3759.1237676491.31690.help-gnu-emacs@gnu.org>
2009-03-22 18:23 ` geoff.bache
2009-03-22 19:08 ` Eli Zaretskii
[not found] ` <mailman.3789.1237749011.31690.help-gnu-emacs@gnu.org>
2009-03-22 19:55 ` geoff.bache [this message]
2009-03-22 21:48 ` Eli Zaretskii
[not found] ` <mailman.3799.1237758495.31690.help-gnu-emacs@gnu.org>
2009-03-23 18:25 ` geoff.bache
2009-03-19 22:14 Geoff Bache
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=754129e2-cab7-43b2-aa97-d81fedc338f0@e35g2000yqc.googlegroups.com \
--to=geoff.bache@gmail.com \
--cc=help-gnu-emacs@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.
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).