From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: damien@cassou.me, 54156@debbugs.gnu.org
Subject: bug#54156: 28.0.91; set-face-attribute with a nil FRAME doesn't change the default
Date: Fri, 25 Feb 2022 15:03:02 +0200 [thread overview]
Message-ID: <83bkyvqet5.fsf@gnu.org> (raw)
In-Reply-To: <87y21zw2ll.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 25 Feb 2022 13:30:14 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: damien@cassou.me, 54156@debbugs.gnu.org
> Date: Fri, 25 Feb 2022 13:30:14 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Does this issue happen only with the nil values of :background? If
> > so, may I ask what do you and Damien think should be the effect of
> > setting the background color of a face to nil?
>
> That there is no background colour on the face -- that's the effect of
> doing that (but only on existing frames).
But that's not what nil does in this case. It means the same as
'unspecified': that you have nothing to say about that particular
attribute. So Emacs does nothing.
Think about it: any face attribute not explicitly mentioned in a
defface is set to 'unspecified' by the low-level code. This is basic
in how faces are handled in Emacs; we cannot easily change that
without breaking gobs of code.
Moreover, attributes of the faces for future frames, the ones you get
by calling face-attribute with FRAME = t, are documented to be
'unspecified' by default.
The correct way to do what Damien wants (AFAIU) is this:
(set-face-attribute 'region nil :background 'unspecified)
(set-face-attribute 'region t :background 'unspecified)
That is, one must explicitly call set-face-attribute with FRAME = t
(as well as nil), and pass 'unspecified' (NOT nil!) as the value.
Maybe we should document that, although it is a obscure and unusual
thing to do.
next prev parent reply other threads:[~2022-02-25 13:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 10:21 bug#54156: 28.0.91; set-face-attribute with a nil FRAME doesn't change the default Damien Cassou
2022-02-25 12:15 ` Lars Ingebrigtsen
2022-02-25 12:26 ` Eli Zaretskii
2022-02-25 12:30 ` Lars Ingebrigtsen
2022-02-25 13:03 ` Eli Zaretskii [this message]
2022-02-25 13:12 ` Lars Ingebrigtsen
2022-02-25 13:24 ` Eli Zaretskii
2022-02-25 15:42 ` bug#54156: [External] : " Drew Adams
2022-02-26 15:04 ` Lars Ingebrigtsen
2022-02-26 15:24 ` Eli Zaretskii
2022-02-26 16:17 ` bug#54156: [External] : " Drew Adams
2022-02-26 16:35 ` Eli Zaretskii
2022-02-26 17:23 ` Drew Adams
2022-02-26 17:50 ` Eli Zaretskii
2022-02-26 22:47 ` Drew Adams
2022-02-27 7:04 ` Eli Zaretskii
2022-02-27 15:49 ` Drew Adams
2022-02-27 13:02 ` Lars Ingebrigtsen
2022-02-27 16:13 ` bug#54156: [External] : " Drew Adams
2022-02-25 12:16 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkyvqet5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54156@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.