GNU bug report logs - #21871
Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting.

Previous Next

Package: emacs;

Reported by: Alan Mackenzie <acm <at> muc.de>

Date: Tue, 10 Nov 2015 16:29:01 UTC

Severity: normal

Found in versions 24.5, 24.4

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Alan Mackenzie <acm <at> muc.de>
To: 21871 <at> debbugs.gnu.org
Cc: Glenn Morris <rgm <at> gnu.org>, Alan Mackenzie <acm <at> 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

In article <mailman.2173.1447351928.7904.bug-gnu-emacs <at> 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).
This bug report was last modified 3 years and 303 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.