From: Richard Stallman <rms@gnu.org>
Subject: [Lute.Kamstra.lists@xs4all.nl: Re: junk in *grep* buffers]
Date: Mon, 11 Apr 2005 14:12:42 -0400 [thread overview]
Message-ID: <E1DL3Os-00008X-F5@fencepost.gnu.org> (raw)
Would someone please investigate this bug?
Please respond to this message if you investigate it.
------- Start of forwarded message -------
To: Dave Love <fx@gnu.org>
In-Reply-To: <rzqd5t8g8x2.fsf@dpcsport.dl.ac.uk> (Dave Love's message of "Tue,
05 Apr 2005 23:23:21 +0100")
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Date: Wed, 06 Apr 2005 01:46:34 +0200
Cc: emacs-pretest-bug@gnu.org
Subject: Re: junk in *grep* buffers
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
Dave Love <fx@gnu.org> writes:
> Escape sequences appear randomly in *grep* buffers, at least on
> lines with two matches. You can get different results from running
> the same grep multiple times, but not reproducibly, and you may not
> see the escapes the first time.
[...]
I've noticed a problem that's likely related.
When I do M-x grep and use
grep -nH -e "(define-minor-mode" lisp/*.el
I get a *grep* buffer with occurrences of "(define-minor-mode" in lisp
files. Every time that I tried, most lines in this buffer give the
text "(define-minor-mode" the grep-match-face, but a few lines don't
fontify "(define-minor-mode". The strange thing is that the lines
that don't fontify "(define-minor-mode" are different every time I
invoke grep.
I've got a sneaky suspicion that something goes awry with the
interaction between font-locking and the code in
grep-mode-font-lock-keywords that removes the escape sequences.
Lute.
_______________________________________________
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
------- End of forwarded message -------
next reply other threads:[~2005-04-11 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 18:12 Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-26 10:06 [Lute.Kamstra.lists@xs4all.nl: Re: junk in *grep* buffers] Richard Stallman
2005-05-10 12:33 ` Kai Großjohann
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=E1DL3Os-00008X-F5@fencepost.gnu.org \
--to=rms@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 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).