From: Alan Mackenzie <acm@muc.de>
To: 21871@debbugs.gnu.org
Cc: Alan Mackenzie <acm@muc.de>
Subject: bug#21871: Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting.
Date: 12 Nov 2015 18:54:24 -0000 [thread overview]
Message-ID: <20151112185424.38599.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.2173.1447351928.7904.bug-gnu-emacs@gnu.org>
In article <mailman.2173.1447351928.7904.bug-gnu-emacs@gnu.org> you wrote:
> On Thu, Nov 12, 2015 at 11:36:55AM -0500, Glenn Morris wrote:
>> Alan Mackenzie wrote:
>> > Thinking about it, this is surely a bug in the documentation.
>> I disagree, since it works as documented in Emacs 24.3.
>> It seems to have been broken since 24.4.
> Thanks for that tip. The code for it (in font-lock-compile-keywords) is
> still there, but somehow one of a list of conditions which prevent it
> being activated has become set.
> I'm looking into it.
The fix to bug #16247 meant no longer setting syntax-begin-function to a
non-nil value. This is the condition which used to cause the appropriate
font-lock-keywords form to get added to lisp-font-lock-keywords-1/2. It
no longer is.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-11-12 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 16:30 bug#21871: Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting Alan Mackenzie
[not found] ` <mailman.2066.1447172952.7904.bug-gnu-emacs@gnu.org>
2015-11-12 12:44 ` Alan Mackenzie
2015-11-12 16:36 ` Glenn Morris
2015-11-12 18:12 ` Alan Mackenzie
[not found] ` <mailman.2173.1447351928.7904.bug-gnu-emacs@gnu.org>
2015-11-12 18:54 ` Alan Mackenzie [this message]
2015-11-12 19:17 ` Eli Zaretskii
2016-05-15 21:50 ` Dmitry Gutov
2016-05-16 10:20 ` Alan Mackenzie
2016-05-16 13:18 ` Dmitry Gutov
2016-05-16 15:00 ` Andreas Röhler
2016-05-17 9:02 ` Alan Mackenzie
2017-09-02 13:19 ` Eli Zaretskii
2020-04-11 15:00 ` Noam Postavsky
2021-09-19 22:14 ` Stefan Kangas
2021-09-20 17:50 ` Alan Mackenzie
2021-09-21 23:07 ` Stefan Kangas
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=20151112185424.38599.qmail@mail.muc.de \
--to=acm@muc.de \
--cc=21871@debbugs.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).