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 15:13:28 +0000 [thread overview]
Message-ID: <SJ0PR10MB548834296E2CCF20FD16ED69F3129@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87eebzk4gf.fsf@gnus.org>
> > Yes, the problem is still there. (Tested, e.g.,
> > with the latest Emacs release, 27.2.)
> >
> > See the recipe from emacs -Q in...
>
> "Multiple simultaneous solution representations in a
> population based evolutionary algorithm"?
Oops - copy+paste error. This is the URL (for msg #11):
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=15740#11
> Are you sure that this isn't a problem with doremi?
> Do you see the problem using `M-x customize-themes'?
Yes - no problem with doremi. `doremi-custom-themes+'
just changes to the next theme when you hit a key
(e.g. <up>).
And with non-nil option `doremi-custom-themes-accumulate-flag'
it does what Emacs does by default when moving to another
theme: it doesn't cancel the previous theme(s); it just
adds (enables) the new one also (uses `enable-theme').
None of this has anything to do with `customize-themes'.
(The comparison is to use `doremi-color-themes+', which
cycles among _color_ themes. The code is parallel.)
next prev parent reply other threads:[~2021-07-15 15:13 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 ` bug#15740: [External] : " Drew Adams
2021-07-15 15:00 ` Lars Ingebrigtsen
2021-07-15 15:13 ` Drew Adams [this message]
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=SJ0PR10MB548834296E2CCF20FD16ED69F3129@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.