From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: maurooaranda@gmail.com, 43265@debbugs.gnu.org,
monnier@iro.umontreal.ca, tsdh@gnu.org
Subject: bug#43265: 28.0.50; Inconsistent fontifying in elisp-mode
Date: Sun, 24 Jan 2021 21:16:33 +0100 [thread overview]
Message-ID: <87y2gioztq.fsf@gnus.org> (raw)
In-Reply-To: <83v9bm2j36.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 24 Jan 2021 22:09:01 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Before this, special forms and macros were handled in the same way, but
>> the commit message doesn't really explain why this was changed.
>
> https://lists.gnu.org/archive/html/emacs-devel/2015-03/msg00327.html
Skimming that thread, I can't see any explanation for why we don't check
that special forms are in a function position, while we do that for
macros?
I.e.,
(setq a '(if a b))
is currently fontified incorrectly, while
(setq a '(when a b))
is fontified correctly.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-24 20:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 20:05 bug#43265: 28.0.50; Inconsistent fontifying in elisp-mode Mauro Aranda
2021-01-22 19:32 ` Lars Ingebrigtsen
2021-01-22 20:11 ` Mauro Aranda
2021-01-22 22:32 ` Stefan Monnier
2021-01-23 18:42 ` Lars Ingebrigtsen
2021-01-23 19:54 ` Stefan Monnier
2021-01-24 19:58 ` Lars Ingebrigtsen
2021-01-24 19:59 ` Lars Ingebrigtsen
2021-01-24 20:09 ` Eli Zaretskii
2021-01-24 20:16 ` Lars Ingebrigtsen [this message]
2021-01-24 21:58 ` bug#43265: [External] : " Drew Adams
2021-01-25 6:30 ` Tassilo Horn
2021-01-25 6:39 ` Lars Ingebrigtsen
2021-01-25 6:46 ` Tassilo Horn
2021-01-25 13:59 ` Stefan Monnier
2021-01-25 23:34 ` Lars Ingebrigtsen
2021-01-25 16:09 ` Drew Adams
2021-01-25 16:14 ` Drew Adams
2021-01-25 16:01 ` Drew Adams
2021-01-24 21:25 ` Stefan Monnier
2021-01-26 0:19 ` Lars Ingebrigtsen
2021-01-26 0:27 ` Mauro Aranda
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2gioztq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43265@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=maurooaranda@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=tsdh@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.