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 14:47:29 +0300 [thread overview]
Message-ID: <83v992clv2.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=gkhHppCgmNCVFfS61uQXRKVYnuUa16BR_PFQhtBaqvQ@mail.gmail.com> (message from Stefan Kangas on Sun, 4 Apr 2021 04:05:43 -0500)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sun, 4 Apr 2021 04:05:43 -0500
> Cc: monnier@iro.umontreal.ca, 47424@debbugs.gnu.org, mardani29@yahoo.es
>
> > With themes, you can load several ones and then enable/disable any of
> > them whenever you see fit.
>
> I don't see why a user would want/need to load a theme if she does not
> intend to use it.
The user does intend to use these themes, just not right away and not
all of them. It's a valid use case to want to switch to another
theme, e.g. because someone wants one theme in the morning and another
in the evening.
> What am I missing?
I don't think you are missing anything, you just disregard everything
I say in response and keep repeating the same claims and questions.
That's not a useful discussion method. I'm tempted to stop responding
because it just wastes my time. Sorry for being blunt.
> > Under your proposal, disabling a theme would be impossible without
> > unloading it, and that might not be easy to do cleanly.
>
> I'm not sure I follow; I see no need to make it symmetrical in that
> sense.
So loading the theme will enable it, but disabling will not unload it?
Then how to I re-enable a theme that was disabled? by loading it the
second time?
> In the same way, we don't bother unloading a library just because
> the major-mode involved is not used in any buffer. But we do
> provide a way to autoload major modes.
Themes are not like modes, they are in effect in the entire Emacs
session, in all of the buffers. You cannot evade a theme by going to
another buffer like you do with modes.
next prev parent reply other threads:[~2021-04-04 11:47 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 [this message]
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=83v992clv2.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).