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 16:44:20 +0300 [thread overview]
Message-ID: <83mtuecggb.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmZYgPyYd304RSckEgay=MtgV_PWrNRbg6qNx7950hezA@mail.gmail.com> (message from Stefan Kangas on Sun, 4 Apr 2021 08:17:04 -0500)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sun, 4 Apr 2021 08:17:04 -0500
> Cc: monnier@iro.umontreal.ca, 47424@debbugs.gnu.org, mardani29@yahoo.es
>
> To put this more concretely, I'd like to see two functions (and let's
> disregard what we have now for the sake of argument):
>
> enable-theme
> disable-theme
>
> Whatever happens technically (loading, autoloading, unloading, etc.) is
> not interesting to the user. What is interesting is that after you run
> one of the above commands the specified theme is either enabled or
> disabled.
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?
next prev parent reply other threads:[~2021-04-04 13:44 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 [this message]
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=83mtuecggb.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).