From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "47047@debbugs.gnu.org" <47047@debbugs.gnu.org>,
Juri Linkov <juri@linkov.net>
Subject: bug#47047: [External] : Re: bug#47047: 28.0.50; 'help-key-binding' face's background sub-optimal
Date: Wed, 29 Sep 2021 19:50:57 +0000 [thread overview]
Message-ID: <SJ0PR10MB548855680A5C9A158A22CA92F3A99@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmmPvCBeQDemH8Zic9vRaVEuffzfqLiHVMoq-r+VvK_Ybg@mail.gmail.com>
> > Do we have some reason to deprecate this theme,
> > beyond someone finding that a new face "looks
> > out of place" when that theme is used?
> > It's always good to see an actual reason.
>
> FWIW, I would personally object to removing a theme
> on non-technical grounds.
>
> In any case, you objected, and AFAIU you are still the maintainer so in
> that sense there is nothing to discuss here. The theme is staying, at
> least until our maintainers say otherwise (the same as for all things).
>
> As for reasons to remove a theme, I wrote before:
>
> "We have more than one theme that is buggy, has low coverage and/or
> is not maintained, so maybe this is something we should think
> about."
>
> I can't say if it is buggy or not, but I think it has low coverage, and
> it is clearly maintained only sparingly.
FWIW, I agree with what you wrote there.
Except for a few nits:
1. IMO, bugginess of a theme should matter (should
be thought about, as you put it), but low usage
(coverage?) should not. Why remove a theme just
because it's seldom used?
2. Once again: I have NOT objected to deleting the
theme. I asked about technical reasons to do so.
3. I have no idea who the "maintainer" of that theme is.
We were asked to contribute themes when custom themes
became a possibility, and I sent that one.
next prev parent reply other threads:[~2021-09-29 19:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 13:40 bug#47047: 28.0.50; 'help-key-binding' face's background sub-optimal Eli Zaretskii
2021-03-10 19:59 ` Juri Linkov
2021-03-10 20:06 ` Eli Zaretskii
2021-03-13 19:01 ` Stefan Kangas
2021-03-13 19:25 ` Stefan Kangas
2021-03-14 3:00 ` bug#47047: [External] : " Drew Adams
2021-03-14 3:39 ` Stefan Kangas
2021-09-28 17:46 ` Stefan Kangas
2021-09-28 20:26 ` bug#47047: [External] : " Drew Adams
2021-09-28 20:54 ` Stefan Kangas
2021-09-28 22:13 ` Drew Adams
2021-09-29 15:57 ` Lars Ingebrigtsen
2021-09-29 16:52 ` Stefan Kangas
2021-09-29 16:56 ` Lars Ingebrigtsen
2021-09-29 17:24 ` Stefan Kangas
2021-09-30 6:22 ` Lars Ingebrigtsen
2021-10-03 0:24 ` Stefan Kangas
2021-10-03 9:05 ` Lars Ingebrigtsen
2021-09-29 17:34 ` bug#47047: [External] : " Drew Adams
2021-09-29 19:18 ` Stefan Kangas
2021-09-29 19:50 ` Drew Adams [this message]
2021-09-29 21:17 ` Stefan Kangas
2021-09-29 22:21 ` Drew Adams
2021-09-29 23:21 ` Stefan Kangas
2021-09-30 1:59 ` Drew Adams
2021-09-28 17:31 ` Stefan Kangas
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=SJ0PR10MB548855680A5C9A158A22CA92F3A99@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=47047@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).