From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64759@debbugs.gnu.org, maurooaranda@gmail.com
Subject: bug#64759: Broken faces
Date: Fri, 21 Jul 2023 21:49:13 +0300 [thread overview]
Message-ID: <86h6pxyubj.fsf@mail.linkov.net> (raw)
In-Reply-To: <83o7k59kpv.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Jul 2023 21:35:08 +0300")
>> Let's see: when the definition is
>>
>> (defface display-time-date-and-time
>> nil
>> "Face for `display-time-format'."
>> :group 'mode-line-faces
>> :version "30.1")
>>
>> then the customization buffer is
>>
>> Hide display-time-date-and-time face: [sample]
>> State : NO CUSTOMIZATION DATA; not intended to be customized.
>> Face for ‘display-time-format’.
>> -- Empty face --
>> Show All Attributes
>>
>> But when the definition is
>>
>> (defface display-time-date-and-time
>> '((t nil))
>> "Face for `display-time-format'."
>> :group 'mode-line-faces
>> :version "30.1")
>>
>> the customization buffer is
>>
>> Hide display-time-date-and-time face: [sample]
>> State : STANDARD.
>> Face for ‘display-time-format’.
>> -- Empty face --
>> Show All Attributes
>>
>> Looks nice. No strange error message about not intended to be customized.
>
> That's not what I asked. I asked about the face attributes.
>
> IOW, isn't
>
> (defface display-time-date-and-time
> '((t nil))
> "Face for `display-time-format'."
> :group 'mode-line-faces
> :version "30.1")
>
> the same as
>
> (defface display-time-date-and-time
> '((t (:inherit default)))
> "Face for `display-time-format'."
> :group 'mode-line-faces
> :version "30.1")
>
> ?
No, it's not the same. The latter uses a white background on the mode line.
next prev parent reply other threads:[~2023-07-21 18:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 6:37 bug#64759: Broken faces Juri Linkov
2023-07-21 7:50 ` Robert Pluim
2023-07-21 8:13 ` Juri Linkov
2023-07-21 10:56 ` Eli Zaretskii
2023-07-21 7:51 ` Eli Zaretskii
2023-07-21 8:13 ` Juri Linkov
2023-07-21 10:48 ` Mauro Aranda
2023-07-21 16:21 ` Juri Linkov
2023-07-21 16:40 ` Eli Zaretskii
2023-07-21 17:51 ` Juri Linkov
2023-07-21 18:35 ` Eli Zaretskii
2023-07-21 18:49 ` Juri Linkov [this message]
2023-07-21 18:55 ` Eli Zaretskii
2023-07-24 17:35 ` Juri Linkov
2023-07-24 18:21 ` Eli Zaretskii
2023-07-25 17:04 ` Juri Linkov
2023-07-25 17:43 ` Eli Zaretskii
2023-07-28 17:30 ` Juri Linkov
2023-07-28 18:49 ` Eli Zaretskii
2023-07-31 17:42 ` Juri Linkov
2023-07-31 18:31 ` Eli Zaretskii
2023-07-31 20:37 ` Mauro Aranda
2023-07-21 10:53 ` Eli Zaretskii
2023-07-21 10:54 ` Eli Zaretskii
2023-07-21 16:20 ` Juri Linkov
2023-07-21 16:39 ` 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=86h6pxyubj.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=64759@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=maurooaranda@gmail.com \
/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).