unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Wilfred Hughes <wilfred@potatolondon.com>
To: Juri Linkov <juri@jurta.org>
Cc: 9408@debbugs.gnu.org
Subject: bug#9408: 23.3; vc-git-grep doesn't link to files when git grep uses colour
Date: Tue, 6 Sep 2011 15:06:45 +0100	[thread overview]
Message-ID: <CAMJPRQzb+H6Qs9=sSDa772xfOiR1UBTan_5VRUQG2Wg85Q5t3w@mail.gmail.com> (raw)
In-Reply-To: <871uvtiybp.fsf@mail.jurta.org>

[-- Attachment #1: Type: text/plain, Size: 655 bytes --]

Oh, sorry. Yes, it can be removed and works perfectly. Many thanks.

On 6 September 2011 14:40, Juri Linkov <juri@jurta.org> wrote:

> > Yes, using git grep without --no-color gets exactly the colour codes you
> > describe. But as of revision 105630 (the commit mentioned in message 13),
> > vc-git-grep uses the command "git grep --no-color -n -e <R> -- <F>" which
> > suppresses search term highlighting. Have I missed something?
>
> You earlier suggested to add "--no-color" to `grep-expand-template'.
> Do you think it now can be removed because now search terms are
> highlighted correctly and you have no more problems with
> hitting RET on them?
>

[-- Attachment #2: Type: text/html, Size: 969 bytes --]

      reply	other threads:[~2011-09-06 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 10:55 bug#9408: 23.3; vc-git-grep doesn't link to files when git grep uses colour Wilfred Hughes
2011-08-30 16:42 ` bug#9408: A simple patch Wilfred Hughes
2011-09-01  7:30   ` Glenn Morris
2011-09-05  8:28 ` bug#9408: 23.3; vc-git-grep doesn't link to files when git grep uses colour Juri Linkov
2011-09-05 12:43   ` Wilfred Hughes
2011-09-06  9:32     ` Juri Linkov
2011-09-06 13:27       ` Wilfred Hughes
2011-09-06 13:40         ` Juri Linkov
2011-09-06 14:06           ` Wilfred Hughes [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

  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='CAMJPRQzb+H6Qs9=sSDa772xfOiR1UBTan_5VRUQG2Wg85Q5t3w@mail.gmail.com' \
    --to=wilfred@potatolondon.com \
    --cc=9408@debbugs.gnu.org \
    --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 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).