From: Stephen Berman <stephen.berman@gmx.net>
To: Boris Buliga <boris@d12frosted.io>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Overriding inherited face attributes
Date: Tue, 27 Nov 2018 22:33:23 +0100 [thread overview]
Message-ID: <87pnuqfboc.fsf@gmx.net> (raw)
In-Reply-To: <CAD5F_-BdnVWDWmznkEjEP9OT0hCef5f_5Ar=tD_QcQoA+o-FKA@mail.gmail.com> (Boris Buliga's message of "Tue, 27 Nov 2018 22:18:45 +0200")
On Tue, 27 Nov 2018 22:18:45 +0200 Boris Buliga <boris@d12frosted.io> wrote:
> Hi everyone,
>
> Sorry if this question was answered somewhere before. I searched and didn't
> find any working solution, so here I am.
>
> Problem. Override a face attribute that is defined in an inherited face.
>
> For example, open up a new buffer in the fundamental mode and evaulate the
> following experssion:
>
> (insert (propertize "hello" 'face '(:foreground "red" :inherit (:foreground
> "orange"))))
>
> I expect the word 'hello' to be red, but instead, it is orange.
>
> So two questions:
>
> 1. Am I right to expect the text to be red?
> 2. How to achieve this?
I don't know the answer to your first questions, but the answer to the
second question appears to be: switch the order. At least, when I
evaluate the following in fundamental mode, 'hello' is red:
(insert (propertize "hello" 'face '(:inherit (:foreground "orange")
:foreground "red")))
In (info "(elisp) Special Properties") it says this: "The value of the
[`face'] property can be... A list of faces... Faces occurring earlier
in the list have higher priority." And in (info "(elisp) Face
Attributes") it says: "Attributes from inherited faces are merged into
the face like an underlying face would be, with higher priority than
underlying faces." Whether this implies the above observed behavior is
not clear to me.
Steve Berman
next prev parent reply other threads:[~2018-11-27 21:33 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 [this message]
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
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=87pnuqfboc.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=boris@d12frosted.io \
--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).