From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Tassilo Horn <tsdh@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"43265@debbugs.gnu.org" <43265@debbugs.gnu.org>,
"maurooaranda@gmail.com" <maurooaranda@gmail.com>
Subject: bug#43265: [External] : bug#43265: 28.0.50; Inconsistent fontifying in elisp-mode
Date: Mon, 25 Jan 2021 08:59:59 -0500 [thread overview]
Message-ID: <jwvpn1tktj5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mtwx7bhc.fsf@gnu.org> (Tassilo Horn's message of "Mon, 25 Jan 2021 07:46:46 +0100")
> Feel free to do so. But I can also make an argument for the current
> behavior: special forms are under our control and there aren't many, so
> if they happen to be in a quoted form, it's likely that's actually code
> eventually being run.
I don't see why that should be more likely for special forms than for
macros. For many of them, which is which is largely an
arbitrary choice.
Stefan
next prev parent reply other threads:[~2021-01-25 13:59 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
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 [this message]
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=jwvpn1tktj5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=43265@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=maurooaranda@gmail.com \
--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.