From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Overriding inherited face attributes
Date: Wed, 28 Nov 2018 21:01:36 +0100 [thread overview]
Message-ID: <87a7lt0y5b.fsf@rub.de> (raw)
In-Reply-To: <831s75fa5q.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Nov 2018 18:18:25 +0200")
On Wed, 28 Nov 2018 18:18:25 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: help-gnu-emacs@gnu.org
>> Date: Wed, 28 Nov 2018 14:13:39 +0100
>>
>> >> (insert (propertize "hello" 'face '(:inherit (:foreground "orange")
>> >> :foreground "red")))
>> >>
>> >> makes the face display as red, and this seems to conflict with the above
>> >> documentation.
>> >
>> > It doesn't, because ':foreground "red"' is not the "underlying face".
>>
>> That occurred to me, but then I have to conclude I really don't
>> understand the doc, according to my reading of which the `inherit'
>> property should have higher priority by virtue of being earlier in the
>> list.
>
> If someone has concrete proposals for how to make the documentation of
> these aspects better, I'm open to suggestions.
It would be helpful to know from precisely which part of the
documentation it follows that evaluating this:
(insert (propertize "hello" 'face '(:foreground "red" :inherit
(:foreground "orange"))))
displays "hello" in orange while evaluating this:
(insert (propertize "hello" 'face '(:inherit (:foreground "orange")
:foreground "red")))
displays "hello" in red. I don't see how it follows from the passage in
the Lisp manual I cited ("Faces occurring earlier in the list have
higher priority") unless "occurring earlier in the list" and "higher
priority" have non-standard meanings, which should then also be defined
in the documentation. And from what you wrote above, the higher
priority of the `inherit' property is irrelevant in these examples,
since as you said "':foreground "red"' is not the "underlying face". So
can you point out the passage(s) in the manual from which the above
observed differences follow? Maybe once I see that I'll be satisfied
with the existing documentation, or else could try to suggest
improvements.
Steve Berman
next prev parent reply other threads:[~2018-11-28 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 20:18 Overriding inherited face attributes Boris Buliga
2018-11-27 21:33 ` Stephen Berman
2018-11-28 6:19 ` Eli Zaretskii
2018-11-28 12:24 ` Stephen Berman
2018-11-28 13:06 ` Eli Zaretskii
2018-11-28 13:13 ` Stephen Berman
2018-11-28 16:18 ` Eli Zaretskii
2018-11-28 20:01 ` Stephen Berman [this message]
2018-11-28 20:35 ` Eli Zaretskii
2018-11-28 21:34 ` Stephen Berman
2018-11-29 7:14 ` Eli Zaretskii
2018-11-29 17:30 ` Stephen Berman
2018-11-28 21:44 ` Boris Buliga
2018-11-29 7:08 ` Eli Zaretskii
2018-11-28 7:39 ` Boris Buliga
2018-11-28 7:51 ` Eli Zaretskii
2018-11-28 8:42 ` Boris Buliga
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=87a7lt0y5b.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).