From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Engster <deng@randomsample.de>
Cc: "18444@debbugs.gnu.org" <18444@debbugs.gnu.org>,
Martin Apel <martin.apel@simpack.de>
Subject: bug#18444: 24.3.93; Error running timer 'compilation-auto-jump' from grep-mode
Date: Sat, 20 Sep 2014 16:41:08 -0400 [thread overview]
Message-ID: <jwvfvfm2fm5.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87fvfmverc.fsf@engster.org> (David Engster's message of "Sat, 20 Sep 2014 11:10:31 +0200")
> I see the following ways to solve this:
> - Following RMS initial idea, use a text property to mark text which
> should not be parsed for errors.
> - Use buffer-local-variables to remember where the actual
> compilation/grep output starts and ends, and use that as an
> lower/upper bound when calling `compilation--parse-region' in
> `compilation--ensure-parse'.
Text properties seem more elegant than buffer-local vars.
> Whatever we do to fix it, I'm leaning towards doing this in trunk.
Sounds OK, yes. IIUC this is not a new bug.
We could add a quick-hack/workaround in emacs-24, but only if it's very
straightforward&safe.
Stefan
next prev parent reply other threads:[~2014-09-20 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 12:24 bug#18444: 24.3.93; Error running timer 'compilation-auto-jump' from grep-mode Martin Apel
2014-09-10 19:09 ` Glenn Morris
2014-09-11 7:06 ` Martin Apel
2014-09-11 15:59 ` Glenn Morris
2014-09-11 23:29 ` Glenn Morris
2014-09-11 23:41 ` Glenn Morris
2014-09-12 6:49 ` Martin Apel
2014-09-20 9:10 ` David Engster
2014-09-20 20:41 ` Stefan Monnier [this message]
2014-09-20 21:40 ` Glenn Morris
2022-02-10 8:19 ` Lars Ingebrigtsen
2022-02-10 8:27 ` APEL Martin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 8:29 ` Lars Ingebrigtsen
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=jwvfvfm2fm5.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18444@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=martin.apel@simpack.de \
/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).