From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 2397@emacsbugs.donarmstrong.com
Subject: bug#2397: 23.0.90; grep no longer highlights the match
Date: Sun, 22 Feb 2009 12:04:02 -0800 [thread overview]
Message-ID: <001601c99528$b5b2e380$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <874oymnvx3.fsf@jurta.org>
> From: Juri Linkov Sent: Sunday, February 22, 2009 11:02 AM
> > Even more specifically, it is the change from
> > (setenv "GREP_OPTIONS" (concat (getenv "GREP_OPTIONS") "
> --color=always"))
> > to
> > (setenv "GREP_OPTIONS" (concat (getenv "GREP_OPTIONS") "
> --color=auto"))
> > that introduces the bug. Putting back `always' in place of
> `auto' restores the
> > highlighting.
> >
> > Why `auto' doesn't work, I don't know.
>
> This change was the result of the following discussion:
>
> http://thread.gmane.org/gmane.emacs.bugs/16956
> http://thread.gmane.org/gmane.emacs.devel/83316
>
> As you can see grep source code emits highlighting sequences
> only when TERM is not "dumb". So we set it to "emacs-grep".
>
> if(isatty(STDOUT_FILENO) && getenv("TERM") &&
> strcmp(getenv("TERM"), "dumb"))
> color_option = 1;
> else
> color_option = 0;
>
> Could you please post the value of `process-connection-type'.
`process-connection-type' has value t.
> Also please eval `M-x grep RET set RET'
Sorry, I don't understand. That does nothing; it just exits with no matches
found - there are no file arguments specified. And in which directory? With
which `grep' switches? I don't follow.
> and show the value of the environment variable `TERM'.
M-: (getenv "TERM) gives "dumb", both in emacs -Q and in my own environment
(i.e., after loading the cywin libraries I mentioned).
> If it is "emacs-grep" then I'm afraid it is the line
> "isatty(STDOUT_FILENO)" in grep source code that fails
> in your environment.
It's not.
And as I mentioned, before your change highlighting works fine.
next prev parent reply other threads:[~2009-02-22 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <utz6eo3ue.fsf@gnu.org>
2009-02-19 23:26 ` bug#2397: 23.0.90; grep no longer highlights the match Drew Adams
2009-02-22 17:56 ` Drew Adams
2009-02-22 19:01 ` Juri Linkov
2009-02-22 20:04 ` Drew Adams [this message]
2009-02-22 22:08 ` Juri Linkov
2009-02-22 22:27 ` Drew Adams
2009-02-22 22:52 ` Juri Linkov
2009-02-22 23:14 ` Drew Adams
2009-02-22 23:48 ` Juri Linkov
2009-02-24 0:56 ` Drew Adams
2009-02-28 17:50 ` bug#2397: marked as done (23.0.90; grep no longer highlights the match) Emacs bug Tracking System
[not found] ` <000701c999ce$aa77cb20$0200a8c0@us.oracle.com>
[not found] ` <usklyo063.fsf@gnu.org>
[not found] ` <001201c999da$77282650$0200a8c0@us.oracle.com>
2009-02-28 20:10 ` bug#2397: 23.0.90; grep no longer highlights the match Eli Zaretskii
2009-02-28 21:09 ` Drew Adams
2009-02-28 22:08 ` Eli Zaretskii
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='001601c99528$b5b2e380$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=2397@emacsbugs.donarmstrong.com \
--cc=juri@jurta.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.