From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: Help with font-lock-add-keywords
Date: Fri, 13 Mar 2015 15:52:06 +0100 [thread overview]
Message-ID: <87mw3h9ch5.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <a023c5e1-c120-4afd-bdc7-eaefd823d537@default>
On 2015-03-13, at 15:37, Drew Adams <drew.adams@oracle.com> wrote:
>> Emacs tried to evaluate the unquoted (and undefined) symbol in the midst
>> of fontifying, so there as an error and the fontifying routine crashed.
>> (Just my suspicion, but seems reasonable.)
>
> In general, errors that occur during font locking are swallowed, on
> purpose. Font lock is pretty much an invisible, background genie that
> does its thing whenever it feels like it, independently of what else
> you might think is going on.
>
> It would generally be inappropriate for such an error to be raised,
> so font lock just gives up at that point, instead of raising it.
Of course. Still, this seems to explain the behavior I saw.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-03-13 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 3:20 Help with font-lock-add-keywords Marcin Borkowski
2015-03-13 3:47 ` Michael Heerdegen
2015-03-13 6:39 ` Marcin Borkowski
2015-03-13 12:31 ` Robert Thorpe
2015-03-13 14:37 ` Drew Adams
2015-03-13 14:52 ` Marcin Borkowski [this message]
[not found] <mailman.1931.1426216826.31049.help-gnu-emacs@gnu.org>
2015-03-13 3:33 ` Emanuel Berg
2015-03-13 3:46 ` Marcin Borkowski
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=87mw3h9ch5.fsf@wmi.amu.edu.pl \
--to=mbork@wmi.amu.edu.pl \
--cc=help-gnu-emacs@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.
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).