From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: damien@cassou.me, larsi@gnus.org, 54156@debbugs.gnu.org
Subject: bug#54156: [External] : bug#54156: 28.0.91; set-face-attribute with a nil FRAME doesn't change the default
Date: Sun, 27 Feb 2022 09:04:38 +0200 [thread overview]
Message-ID: <8335k4pz7d.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488A2951CFF5E7898B03F7EF33F9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sat, 26 Feb 2022 22:47:41 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "larsi@gnus.org" <larsi@gnus.org>, "damien@cassou.me" <damien@cassou.me>,
> "54156@debbugs.gnu.org" <54156@debbugs.gnu.org>
> Date: Sat, 26 Feb 2022 22:47:41 +0000
>
> > I didn't say to use only t.
>
> I didn't say you did say to use only t.
>
> You said to use both (separately). My question was
> why to bother _also_ using `t'.
Because it's future-proof. And because resetting a color attribute to
'unspecified' so that it overrides the defface is an unusual thing to
do, and so it better stands out in the code, telling everyone that
this is the intent.
next prev parent reply other threads:[~2022-02-27 7:04 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
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 [this message]
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
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=8335k4pz7d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54156@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=drew.adams@oracle.com \
--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 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).