From: Juri Linkov <juri@jurta.org>
To: Sam Steingold <sds@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: M-x grep: broken buffer with pipes
Date: Thu, 31 Dec 2009 02:32:12 +0200 [thread overview]
Message-ID: <87tyv8yodv.fsf@mail.jurta.org> (raw)
In-Reply-To: <4B3BB2C6.9070700@gnu.org> (Sam Steingold's message of "Wed, 30 Dec 2009 15:06:30 -0500")
> M-x grep RET 'defvar.*buffer' *.el | grep -v '"' RET
> (the shell command is "grep -nH -e 'defvar.*buffer' *.el | grep -v '"'")
> The *grep* buffer now contains (correctly) about 10% fewer matches, and
> <file> and <line> are still good, but the <defvar foo-buffer> part is no
> longer yellow.
You can customize `grep-highlight-matches' to the value `always'
if you are content with the problems it might cause like
http://thread.gmane.org/gmane.emacs.devel/83316
> That lack of match highlighting is not a big deal, however, there is
> a hugely more horrible problem: one cannot click on the file name to visit
> the file.
> When you click on the file name, the file selection menu appears, with the
> default being ^[[K<file> where "^[" stands for the escape character (ESC
> (27, #o33, #x1b)) and <file> is the file name you clicked on.
> So, where do these 3 spurious characters (ESC [ K) come from?
I guess these escape sequences come from the grep switch --color that
outputs them around the matched strings. However, I can't reproduce your
problem. When I click on the file name that lacks of match highlighting,
it still visits the source file. What grep version do you have?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-12-31 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 20:06 M-x grep: broken buffer with pipes Sam Steingold
2009-12-31 0:32 ` Juri Linkov [this message]
2009-12-31 0:50 ` Sam Steingold
2009-12-31 1:08 ` Juri Linkov
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=87tyv8yodv.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=sds@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.
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.