From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 51e7e46: Font-lock elisp macros/special forms dynamically
Date: Mon, 16 Mar 2015 08:41:39 +0100 [thread overview]
Message-ID: <87wq2h2xu4.fsf@gnu.org> (raw)
In-Reply-To: <jwvbnjuaxbm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 15 Mar 2015 15:15:57 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Instead of updating a big macro regexp after load, there should be a
>> `declare' attribute that would let specific macros (and functions)
>> opt into being fontified specially.
>
> Maybe the other way around would be better: add a declaration that
> says "this macro faithfully mimicks the behavior of a function".
Both opt-in and opt-out sound reasonable to me, and I don't have a
preference. So just tell me what you prefer.
AFAICS, I'd need to add a new `(no-)font-lock-keyword' entry to
`macro-declarations-alist' and then check (get macro
'(no-)font-lock-keyword) in the code building the regex, right? Or in
case of opt-in, (declare 'font-lock-keyword) could add the symbol to a
list of macros to font-lock as keywords so that we don't need to check
all symbols in `obarray'.
The name (no-)font-lock-keyword is open to discussion, of course.
Also, I'd like to rename the new lisp--el-*-macro-* symbols to
lisp--el-*-keyword-* since they deal with both macros and special forms,
i.e., they deal with stuff font-locked with keyword face.
Bye,
Tassilo
next prev parent reply other threads:[~2015-03-16 7:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150315082509.21193.18465@vcs.savannah.gnu.org>
[not found] ` <E1YX3rB-0005WV-PA@vcs.savannah.gnu.org>
2015-03-15 9:12 ` [Emacs-diffs] master 51e7e46: Font-lock elisp macros/special forms dynamically Daniel Colascione
2015-03-15 15:11 ` Artur Malabarba
2015-03-15 17:20 ` Drew Adams
2015-03-15 19:15 ` Stefan Monnier
2015-03-16 1:35 ` Artur Malabarba
2015-03-16 3:07 ` Stefan Monnier
2015-03-16 7:07 ` Tassilo Horn
2015-03-16 7:10 ` Daniel Colascione
2015-03-16 7:54 ` Tassilo Horn
2015-03-16 9:36 ` Tassilo Horn
2015-03-16 12:58 ` Stefan Monnier
2015-03-16 14:47 ` Tassilo Horn
2015-03-16 17:31 ` Stefan Monnier
2015-03-16 20:26 ` Tassilo Horn
2015-03-16 20:39 ` Daniel Colascione
2015-03-16 20:56 ` Stefan Monnier
2015-03-17 9:36 ` Tassilo Horn
2015-03-17 10:17 ` Artur Malabarba
2015-03-17 16:34 ` Stefan Monnier
2015-03-17 16:47 ` Nicolas Richard
2015-03-18 7:17 ` Tassilo Horn
2015-03-18 9:10 ` Artur Malabarba
2015-03-18 9:20 ` Dmitry Gutov
2015-03-18 13:13 ` Stefan Monnier
2015-03-18 16:12 ` Tassilo Horn
2015-03-18 16:44 ` Stefan Monnier
2015-03-16 12:56 ` Stefan Monnier
2015-03-16 7:41 ` Tassilo Horn [this message]
2015-03-16 12:59 ` Stefan Monnier
2015-03-16 14:23 ` Artur Malabarba
2015-03-15 15:09 ` Artur Malabarba
2015-03-16 6:40 ` [Emacs-diffs] " Tassilo Horn
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=87wq2h2xu4.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.