From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "15740@debbugs.gnu.org" <15740@debbugs.gnu.org>
Subject: bug#15740: [External] : Re: bug#15740: 24.3.50; enabling & disabling custom themes is slow
Date: Thu, 15 Jul 2021 14:55:23 +0000 [thread overview]
Message-ID: <SJ0PR10MB548816150D384F0ED0A961A5F3129@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87tukwp21s.fsf@gnus.org>
> > Not so, custom themes - disabling all enabled themes
> > and then enabling one theme is painfully slow, and you see all of the
> > changes manifested on the screen, slowly.
>
> I tried to reproduce this with
>
> M-x customize-themes RET
>
> and then selecting different themes, and I didn't see any particular
> slowness. Are you still seeing this issue in recent versions of Emacs?
>
> (A theme can contain arbitrary code, of course, so it can be arbitrarily
> slow, but that's up to the theme author.)
Yes, the problem is still there. (Tested, e.g.,
with the latest Emacs release, 27.2.)
See the recipe from emacs -Q in https://arxiv.org/abs/2106.05096
Use C-x 5 2 a few times to get multiple frames.
Set option `doremi-custom-themes-accumulate' to
non-nil. (That's the _default_ Emacs behavior,
I believe: to accumulate themes, instead of
replacing the last one with the next one.)
Use `M-x doremi-custom-themes+' to cycle among
the themes provided by default (`emacs -Q').
See that same message for how to compare with
color themes.
I'm using MS Windows. Dunno whether that makes
a difference.
next prev parent reply other threads:[~2021-07-15 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 21:07 bug#15740: 24.3.50; enabling & disabling custom themes is slow Drew Adams
2013-10-28 1:32 ` Leo Liu
2013-10-28 3:08 ` Drew Adams
2021-07-15 5:40 ` Lars Ingebrigtsen
2021-07-15 14:55 ` Drew Adams [this message]
2021-07-15 15:00 ` bug#15740: [External] : " Lars Ingebrigtsen
2021-07-15 15:13 ` Drew Adams
2021-07-15 15:40 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB548816150D384F0ED0A961A5F3129@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=15740@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.