unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Overriding inherited face attributes
Date: Wed, 28 Nov 2018 09:51:06 +0200	[thread overview]
Message-ID: <83d0qpfxn9.fsf@gnu.org> (raw)
In-Reply-To: <CAD5F_-Aarn2crEEFRzi5PT-6=mk4vNq_ZrDwHM6VYNv6J6mT2Q@mail.gmail.com> (message from Boris Buliga on Wed, 28 Nov 2018 09:39:29 +0200)

> From: Boris Buliga <boris@d12frosted.io>
> Date: Wed, 28 Nov 2018 09:39:29 +0200
> Cc: help-gnu-emacs@gnu.org
> 
>   > (propertize "hello" 'face '(:foreground "red" :inherit (:foreground
> "orange")))
>   #("hello" 0 5 (face (:foreground "red" :inherit (:foreground "orange"))))
>   ;; results in an orange text
> 
>   > (propertize "hello" 'face '((:foreground "red") (:inherit (:foreground
> "orange"))))
>   #("hello" 0 5 (face ((:foreground "red") (:inherit ...))))
>   ;; results in a red text
> 
> To me, it's still confusing. Why in the first example I have an orange text
> and
> in the second one - red?

Isn't the second example simply wrong syntax-wise?  Why did you use an
extra level of parentheses?

> 2. And there is a part saying something I don't quite understand about
> inheritance.
> 
> > Attributes from inherited faces are merged into the face like an
> underlying
> > face would be, with higher priority than underlying faces.
> 
> This one looks good to me. If I understand this correctly - inherited face
> attributes behave as usual face attributes.

They behave the same as attributes of the underlying face, but they
override the underlying face where both specify the same attributes.



  reply	other threads:[~2018-11-28  7:51 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
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 [this message]
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=83d0qpfxn9.fsf@gnu.org \
    --to=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).