From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Markus Triska <triska@metalevel.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
35005@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#35005: 27.0.50; Fontification unexpectedly works with anonymous faces
Date: Sat, 09 Nov 2019 13:01:05 -0500 [thread overview]
Message-ID: <jwva795ue1u.fsf-monnier+emacs__47010.6895243347$1573322552$gmane$org@gnu.org> (raw)
In-Reply-To: <87y2wpndxs.fsf@metalevel.at> (Markus Triska's message of "Sat, 09 Nov 2019 18:43:11 +0100")
> 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?
No, the `face FACE` *cannot* be omitted: the `face' symbol in the car is
tested to distinguish this case. Note also that the `PROP1 VAL1 ...`
are *not* face properties, they are *text* properties.
The above docstring should probably replace "face name" by "face" but
other than that it looks about right.
Stefan
next prev parent reply other threads:[~2019-11-09 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 16:37 bug#35005: 27.0.50; Fontification unexpectedly works with anonymous faces Markus Triska
2019-03-28 16:14 ` Eli Zaretskii
2019-10-31 17:24 ` Lars Ingebrigtsen
2019-10-31 20:38 ` Stefan Monnier
2019-11-01 13:13 ` Lars Ingebrigtsen
[not found] ` <871rur4u4j.fsf@gnus.org>
2019-11-02 9:10 ` Markus Triska
[not found] ` <87sgn6abjw.fsf@metalevel.at>
2019-11-02 15:07 ` Lars Ingebrigtsen
[not found] ` <87mudee2pk.fsf@gnus.org>
2019-11-09 17:43 ` Markus Triska
[not found] ` <87y2wpndxs.fsf@metalevel.at>
2019-11-09 18:01 ` Stefan Monnier [this message]
[not found] ` <jwva795ue1u.fsf-monnier+emacs@gnu.org>
2019-11-09 20:02 ` Lars Ingebrigtsen
[not found] ` <87tv7czulh.fsf@gnus.org>
2019-11-09 21:02 ` Markus Triska
[not found] ` <87imnszrsx.fsf@metalevel.at>
2019-11-09 21:10 ` Stefan Monnier
[not found] ` <jwvd0e0u5f7.fsf-monnier+emacs@gnu.org>
2019-11-09 21:29 ` Markus Triska
2019-11-14 9:00 ` Eli Zaretskii
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='jwva795ue1u.fsf-monnier+emacs__47010.6895243347$1573322552$gmane$org@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=35005@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=triska@metalevel.at \
/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).