all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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, 28 Jul 2023 20:30:44 +0300	[thread overview]
Message-ID: <86v8e4lz43.fsf@mail.linkov.net> (raw)
In-Reply-To: <835y67q42w.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 25 Jul 2023 20:43:51 +0300")

>> >> The semantics of nil could be the same as '((t nil)).
>> >
>> > And what is the semantics of '((t nil)) ?  What attributes will the
>> > face have when realized?
>>
>> No attributes.  This is the standard value used by empty faces.
>
> What does this mean?  For example, what would be the foreground color?
> what would be the font? etc.

No foreground color, and no font.

> I'm not familiar with "empty face" notion.  A face always has
> attributes when it is fully realized, otherwise Emacs will be unable
> to use it.

"Empty face" is the standard notion.  Here's an example how it's used:

1. M-x make-empty-face RET foo RET
2. M-x customize-face RET foo RET

Then output is:

  Hide Foo face: [sample]
      State : NO CUSTOMIZATION DATA; not intended to be customized.
     nil
     -- Empty face --

>> >> Do you agree that currently the value '((t nil))
>> >> should be used for faces without default face attributes?
>> >
>> > Yes, I think so.  If no better face to inherit from is available in
>> > each such case, that is.
>>
>> This means these faces should have by default '((t nil)):
>> semantic-decoration-on-includes, shr-h4, shr-h5, shr-h6,
>> nxml-text, nxml-delimiter, nxml-element-colon, makefile-shell
>> as before?
>
> Only if "no better face to inherit from is available" in all of those
> cases.  Which I'm not sure is true.  If you are sure, please tell why
> the faces I put there are not better ideas.

Because they will cause the same problem as with display-time-date-and-time,
except that other faces are used less often, so it will take time until users
will notice these problems.





  reply	other threads:[~2023-07-28 17:30 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86v8e4lz43.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 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.