From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 47424@debbugs.gnu.org, monnier@iro.umontreal.ca, mardani29@yahoo.es
Subject: bug#47424: 28.0.50; enable-theme shows an empty list
Date: Sun, 04 Apr 2021 10:28:30 +0300 [thread overview]
Message-ID: <83czvaecf5.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnZZbmuzE3irWXQDLFM7seLPgaipOg7dh6iuHFxSSNziQ@mail.gmail.com> (message from Stefan Kangas on Sat, 3 Apr 2021 19:14:29 -0500)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 3 Apr 2021 19:14:29 -0500
> Cc: 47424@debbugs.gnu.org, Daniel Martín <mardani29@yahoo.es>
>
> I'm not exactly sure why we bother differentiating between loading a
> theme and enabling it. Technically, I understand that there is a
> difference. But why should a user have to fiddle around with it?
For the same reason that loading a Lisp package shouldn't change the
Emacs state, until the user explicitly activates the features in the
package. It's unclean to have loading activate stuff, and we've
invested an effort during the last years to remove that uncleanliness.
With themes, you can load several ones and then enable/disable any of
them whenever you see fit. Under your proposal, disabling a theme
would be impossible without unloading it, and that might not be easy
to do cleanly.
next prev parent reply other threads:[~2021-04-04 7:28 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 [this message]
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
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=83czvaecf5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47424@debbugs.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).