From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>, help-gnu-emacs@gnu.org
Subject: RE: Help with font-lock-add-keywords
Date: Fri, 13 Mar 2015 07:37:08 -0700 (PDT) [thread overview]
Message-ID: <a023c5e1-c120-4afd-bdc7-eaefd823d537@default> (raw)
In-Reply-To: <87mw3he6zg.fsf@wmi.amu.edu.pl>
> 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.
next prev parent reply other threads:[~2015-03-13 14:37 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 [this message]
2015-03-13 14:52 ` Marcin Borkowski
[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=a023c5e1-c120-4afd-bdc7-eaefd823d537@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).