From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47424@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>,
monnier@iro.umontreal.ca, mardani29@yahoo.es
Subject: bug#47424: 28.0.50; enable-theme shows an empty list
Date: Mon, 27 Jun 2022 10:36:31 +0200 [thread overview]
Message-ID: <87a69y7bao.fsf@gnus.org> (raw)
In-Reply-To: <83mtuecggb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Apr 2021 16:44:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> This (a) turns the table on what we currently do, since currently
> load-theme can optionally enable the theme, while you propose to do it
> the other way around; (b) rocks the very delicate boat of how themes
> are enable, disabled, and prioritized and how they interact with face
> setup, so if we go that way, we should expect quite a rocky ride
> (suggested reading: custom.el). Is it really worth that?
I think the current separation is vaguely useful -- i.e., enable-theme
limits to the currently loaded themes, while load-theme can load and
enable any themes.
So I agree with Eli that we shouldn't change this, and I'm closing this
bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-06-27 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 21:41 bug#47424: 28.0.50; enable-theme shows an empty list Stefan Monnier
2021-03-27 1:50 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-27 1:57 ` Stefan Monnier
2021-03-27 2:40 ` Stefan Monnier
2021-03-27 6:10 ` Eli Zaretskii
2021-04-04 0:14 ` Stefan Kangas
2021-04-04 7:28 ` Eli Zaretskii
2021-04-04 9:05 ` Stefan Kangas
2021-04-04 11:47 ` Eli Zaretskii
2021-04-04 13:17 ` Stefan Kangas
2021-04-04 13:44 ` Eli Zaretskii
2022-06-27 8:36 ` Lars Ingebrigtsen [this message]
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=87a69y7bao.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47424@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
--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).