From: "Drew Adams" <drew.adams@oracle.com>
To: <geoff.bache@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Weird stuff printed out by emacs rgrep
Date: Sat, 21 Mar 2009 15:32:56 -0700 [thread overview]
Message-ID: <004a01c9aa74$fbff2360$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <9ed8d2c9-e755-4c7c-9176-e5e97769c0d2@w34g2000yqm.googlegroups.com>
> Is this perhaps an emacs bug? It would seem perfectly possible to
> instead start something like
> /bin/tcsh -c "env GREP_OPTIONS=' --color=always' find ..."
> which would avoid the problem and any other similar potential
> problems.
Perhaps someone reading your post here can give you an authoritative answer.
But I would say that the best way to find out whether some behavior you find
problematic is in fact a bug is to report it as a bug (with a precise recipe for
reproducing the behavior, starting with emacs -Q).
People reading the bug reports are generally the best placed to filter such
observations and pronounce whether something is a bug or not. help-gnu-emacs
might help you in this regard, but `M-x report-emacs-bug' is probably a better
target for your question.
Especially if you are interested in discussing possible fixes (e.g. "it would
seem perfectly possible to..."), file a bug report and you will likely get the
informed discussion you seek.
There is no need to be certain that something is a bug before you file a bug
report. And there's no shame in mistakenly thinking some behavior is wrong or in
not understanding something completely. Go for it.
next prev parent reply other threads:[~2009-03-21 22:32 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 [this message]
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
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='004a01c9aa74$fbff2360$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=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).