From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 64759@debbugs.gnu.org, maurooaranda@gmail.com
Subject: bug#64759: Broken faces
Date: Mon, 24 Jul 2023 21:21:08 +0300 [thread overview]
Message-ID: <83ila9qigb.fsf@gnu.org> (raw)
In-Reply-To: <86351d5i22.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 24 Jul 2023 20:35:17 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: maurooaranda@gmail.com, 64759@debbugs.gnu.org
> Date: Mon, 24 Jul 2023 20:35:17 +0300
>
> >> No, it's not the same. The latter uses a white background on the mode line.
> >
> > So I ask again: what is the semantics of nil in this case? We cannot
> > have in Emacs something that triggers undefined behavior, let alone
> > use it in our own sources. The semantics of this must be known and
> > documented before we can use it.
>
> 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?
> 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.
next prev parent reply other threads:[~2023-07-24 18:21 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 [this message]
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=83ila9qigb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64759@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).