From: Markus Triska <triska@metalevel.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
35005@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: bug#35005: 27.0.50; Fontification unexpectedly works with anonymous faces
Date: Sat, 09 Nov 2019 18:43:11 +0100 [thread overview]
Message-ID: <87y2wpndxs.fsf@metalevel.at> (raw)
In-Reply-To: <87mudee2pk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 02 Nov 2019 16:07:51 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It just mentions one example where named faces are required, and I think
> the reader will take from that that Emacs will document when you can't
> use anonymous faces. Since font locking doesn't say anything about
> that, then the natural interpretation is that font locking doesn't
> require named faces.
Please consider specifically the documentation of the function
font-lock-add-keywords that I used in the example. Its documentation
points to that of font-lock-keywords, which contains the description:
FACENAME is an expression whose value is the face name to use.
Instead of a face, FACENAME can evaluate to a property list of
the form (face FACE PROP1 VAL1 PROP2 VAL2 ...) in which case all
the listed text-properties will be set rather than just FACE.
This currently states that a face name is expected.
Since the Elisp documentation also states: "Unless otherwise stated, we
will use the term “face” to refer only to named faces.", the notion of
"face" in the description above also does not include anonymous faces.
Would it work to mention that "face FACE" can also be omitted, i.e.,
that an anonymous face can also be specified here?
Thank you and all the best,
Markus
next prev parent reply other threads:[~2019-11-09 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m25zs54mof.fsf@metalevel.at>
[not found] ` <83r2arj7rv.fsf@gnu.org>
2019-10-31 17:24 ` bug#35005: 27.0.50; Fontification unexpectedly works with anonymous faces Lars Ingebrigtsen
2019-10-31 20:38 ` Stefan Monnier
2019-11-01 13:13 ` Lars Ingebrigtsen
2019-11-02 9:10 ` Markus Triska
2019-11-02 15:07 ` Lars Ingebrigtsen
2019-11-09 17:43 ` Markus Triska [this message]
2019-11-09 18:01 ` Stefan Monnier
2019-11-09 20:02 ` Lars Ingebrigtsen
2019-11-09 21:02 ` Markus Triska
2019-11-09 21:10 ` Stefan Monnier
2019-11-09 21:29 ` Markus Triska
2019-11-10 1:52 ` Drew Adams
2019-10-31 21:09 ` Markus Triska
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2wpndxs.fsf@metalevel.at \
--to=triska@metalevel.at \
--cc=35005@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).