GNU bug report logs - #43265
28.0.50; Inconsistent fontifying in elisp-mode

Previous Next

Package: emacs;

Reported by: Mauro Aranda <maurooaranda <at> gmail.com>

Date: Mon, 7 Sep 2020 20:06:02 UTC

Severity: minor

Tags: confirmed

Found in version 28.0.50

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 43265 <at> debbugs.gnu.org, Mauro Aranda <maurooaranda <at> gmail.com>, Tassilo Horn <tsdh <at> gnu.org>
Subject: bug#43265: 28.0.50; Inconsistent fontifying in elisp-mode
Date: Sun, 24 Jan 2021 20:58:22 +0100
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>>>> All special forms get it (`if' is a special form), but macros (like
>>>> `when') only gets it if we're in a funcall position:
>>> Not sure why that is.  Seems like an accident.
>> The special form bit, or the macro bit?  :-)
>
> The fact that the two are treated differently.

The handling of the macros is "more correct".  Should we just remove the
special-casing of special forms?

It apparently was introduced by:

commit 9fdc166ee0ca212f7d5bf1cd9e1177932b0cd9aa
Author:     Tassilo Horn <tsdh <at> gnu.org>
AuthorDate: Mon Mar 16 10:25:14 2015 +0100

Before this, special forms and macros were handled in the same way, but
the commit message doesn't really explain why this was changed.

(Tassilo added to the CCs.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 4 years and 172 days ago.

Previous Next


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