From: Juri Linkov <juri@jurta.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Ulrich Neumerkel <ulrich@complang.tuwien.ac.at>,
schwab@linux-m68k.org, 4359@debbugs.gnu.org
Subject: bug#4359: 23.1.50; ^G in M-x grep mode with git grep
Date: Fri, 01 Jul 2011 04:11:01 +0300 [thread overview]
Message-ID: <878vsi4xga.fsf@mail.jurta.org> (raw)
In-Reply-To: <m3tyb6oomk.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 01 Jul 2011 02:01:23 +0200")
>>>Are there any reasons why `M-x grep' and friends
>>>(i.e. `compilation-start', really) shouldn't bind
>>>`process-connection-type' to nil?
>>
>> M-x grep highlights the actual matches. So this is not a simple pipe.
>
> Right, so when grep detects that it's not a PTY, it switches the
> GREP_COLOR(S) stuff off? And there's no way to force that to be on?
Yes, grep switches colors off if it's not a PTY:
http://thread.gmane.org/gmane.emacs.devel/83316/focus=83449
next prev parent reply other threads:[~2011-07-01 1:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 16:09 bug#4359: 23.1.50; ^G in M-x grep mode with git grep Ulrich Neumerkel
2009-09-06 16:57 ` Andreas Schwab
2009-09-06 17:05 ` Ulrich Neumerkel
2009-09-06 17:15 ` Andreas Schwab
2011-06-30 23:44 ` Lars Magne Ingebrigtsen
2011-06-30 23:50 ` Ulrich Neumerkel
2011-07-01 0:01 ` Lars Magne Ingebrigtsen
2011-07-01 1:11 ` Juri Linkov [this message]
2011-07-01 6:58 ` Jan Djärv
2011-07-01 10:13 ` Lars Magne Ingebrigtsen
2011-07-01 16:48 ` Dan Nicolaescu
2011-07-02 12:35 ` Lars Magne Ingebrigtsen
2022-05-05 12:42 ` bug#4359: bug#15775: 24.3.50; "WARNING: terminal is not fully functional" in Comint and Eshell Lars Ingebrigtsen
2022-06-02 13:07 ` Lars Ingebrigtsen
2022-06-04 17:37 ` Dmitry Gutov
2022-06-05 14:15 ` bug#4359: " Lars Ingebrigtsen
2009-09-06 17:37 ` bug#4359: 23.1.50; ^G in M-x grep mode with git grep Sven Joachim
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=878vsi4xga.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=4359@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.org \
--cc=ulrich@complang.tuwien.ac.at \
/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).