From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "53636@debbugs.gnu.org" <53636@debbugs.gnu.org>,
"tsdh@gnu.org" <tsdh@gnu.org>
Subject: bug#53636: [External] : bug#53636: 29.0.50; face-remapping broken on master
Date: Sat, 5 Feb 2022 16:14:04 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488A11646CCF7FD3F693738F32A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83y22p21na.fsf@gnu.org>
> > > No, it isn't. We had examples with hundreds of faces, back when we
> > > decided to store faces in a hash-table.
> >
> > Sorry, I don't follow -- examples of what that had hundreds of faces?
>
> People reported they have hundreds of faces defined in their Emacs
> sessions. See this message, for example:
>
> https://urldefense.com/v3/__https://lists.gnu.org/archive/html/emacs-
> devel/2021-
> 05/msg01031.html__;!!ACWV5N9M2RV99hQ!eDGeVB_SQ0DAF1rV2RiFjVAIlEJnGK9tdVR-
> 2Epb6b7dlLp0UTSPD7Lm6l0_-q5Y$
>
> It reports to have 600 to 800 faces defined (with 129 in "emacs -Q").
Yes. FWIW, I have 475.
> All that just to have one face that mode-line-* and header-line
> etc. can inherit from? Doesn't this look like a tail wagging the dog?
Right. IMO, no such inheritance should be predefined.
If any user ever _wants_ a particular face to inherit
from another face she can easily do so. Emacs should
not be predefining any such couplings.
next prev parent reply other threads:[~2022-02-05 16:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 13:52 bug#53636: 29.0.50; face-remapping broken on master Tassilo Horn
2022-01-30 17:41 ` Lars Ingebrigtsen
2022-01-30 18:27 ` Eli Zaretskii
2022-01-30 18:31 ` Lars Ingebrigtsen
2022-01-30 19:19 ` Eli Zaretskii
2022-01-30 20:25 ` Eli Zaretskii
2022-01-30 20:28 ` Lars Ingebrigtsen
2022-01-31 12:20 ` Eli Zaretskii
2022-01-31 19:44 ` Eli Zaretskii
2022-02-01 19:38 ` Lars Ingebrigtsen
2022-02-01 20:09 ` Eli Zaretskii
2022-02-02 17:59 ` Lars Ingebrigtsen
2022-02-02 18:07 ` Eli Zaretskii
2022-02-02 19:48 ` Lars Ingebrigtsen
2022-02-02 21:12 ` bug#53636: [External] : " Drew Adams
2022-02-03 6:53 ` Eli Zaretskii
2022-02-03 19:24 ` Lars Ingebrigtsen
2022-02-03 19:53 ` Eli Zaretskii
2022-02-05 6:20 ` Lars Ingebrigtsen
2022-02-05 7:50 ` Eli Zaretskii
2022-02-05 16:14 ` Drew Adams [this message]
2022-02-05 22:27 ` Lars Ingebrigtsen
2022-02-06 7:12 ` Eli Zaretskii
2022-02-06 23:16 ` Lars Ingebrigtsen
2022-02-07 15:03 ` Eli Zaretskii
2022-02-08 6:08 ` Lars Ingebrigtsen
2022-02-08 8:58 ` martin rudalics
2022-02-08 12:41 ` Eli Zaretskii
2022-02-08 18:24 ` martin rudalics
2022-02-08 18:57 ` Eli Zaretskii
2022-02-08 12:29 ` Eli Zaretskii
2022-02-09 8:01 ` Lars Ingebrigtsen
2022-02-09 13:57 ` Eli Zaretskii
2022-02-12 12:20 ` Eli Zaretskii
2022-02-13 8:20 ` Lars Ingebrigtsen
2022-02-13 8:31 ` Tassilo Horn
2022-02-15 9:31 ` Tassilo Horn
2022-02-13 11:58 ` Eli Zaretskii
2022-02-14 10:38 ` Lars Ingebrigtsen
2022-02-03 18:30 ` 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=SJ0PR10MB5488A11646CCF7FD3F693738F32A9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=53636@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=tsdh@gnu.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).