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: Fri, 21 Jul 2023 13:54:33 +0300 [thread overview]
Message-ID: <83a5vp1qmu.fsf@gnu.org> (raw)
In-Reply-To: <86bkg53cau.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 21 Jul 2023 11:13:13 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 64759@debbugs.gnu.org, Mauro Aranda <maurooaranda@gmail.com>
> Date: Fri, 21 Jul 2023 11:13:13 +0300
>
> It seems adding non-empty definitions in bug#64655
> were intended to workaround a bug in cus-edit.el,
> not to fix it.
I don't think it's a bug. Why is it a bug to tell the user that the
face has no information to show as the current definition?
Moreover, what does it mean to have nil there in defface? The
meaning of nil is not documented anywhere that I could see, so what
did the authors of such code expect it to produce?
next prev parent reply other threads:[~2023-07-21 10:54 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
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 [this message]
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=83a5vp1qmu.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 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.