From: Drew Adams <drew.adams@oracle.com>
To: "William G. Gardella" <wgg2@member.fsf.org>
Cc: 15687@debbugs.gnu.org
Subject: bug#15687: 24.3.50; custom themes: disabling does not restore initial configuration
Date: Tue, 26 Nov 2013 11:01:53 -0800 (PST) [thread overview]
Message-ID: <e8fd319e-7f56-49ee-9a5f-93022c281740@default> (raw)
In-Reply-To: <87d2ln9f0b.fsf@motoko.kusanagi>
Please read the bug report. It includes the case where all themes
that have ever been applied have since been disabled. That does not
restore all other customizations that were in effect before theming.
That's all.
If you need a recipe, emacs -Q, load oneonone.el, then doremi.el and
doremi-cmd.el. Then cycle among themes, using `doremi-custom-themes+'.
Use `C-g' to cancel. The initial state is not restored. Nothing
close to it. Not for any existing frames.
Sure, if you then create a new frame, things will look generally OK
in that frame. But the state of any existing frames has been altered
and not restored. Disabling a theme does not undo its effect wrt
Emacs in general. It simply disables one theme wrt other themes
(including wrt all other themes).
In addition, I see no way to take a snapshot of the current Emacs
state as a theme, or even as a pseudo theme, to which one can revert.
This is something that is trivial with color themes - just call
`color-theme-make-snapshot'.
Try the same thing, but with command `doremi-color-themes+'.
No problem.
next prev parent reply other threads:[~2013-11-26 19:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 20:55 bug#15687: 24.3.50; custom themes: disabling does not restore initial configuration Drew Adams
2013-11-26 2:14 ` Stefan Monnier
2013-11-26 14:05 ` Drew Adams
2013-11-26 20:16 ` Stefan Monnier
2013-11-26 20:44 ` Drew Adams
2013-11-30 8:57 ` Glenn Morris
2013-11-30 17:10 ` Drew Adams
2014-11-05 3:48 ` Drew Adams
2018-06-14 19:53 ` Stefan Monnier
2013-11-26 14:08 ` Drew Adams
2013-11-26 18:47 ` William G. Gardella
2013-11-26 19:01 ` Drew Adams [this message]
2013-11-26 19:44 ` W. Greenhouse
2013-11-26 21:16 ` Drew Adams
2015-12-26 1:08 ` Lars Ingebrigtsen
2015-12-26 4:28 ` Drew Adams
2018-06-13 16:41 ` Basil L. Contovounesios
2018-06-14 20:03 ` Stefan Monnier
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=e8fd319e-7f56-49ee-9a5f-93022c281740@default \
--to=drew.adams@oracle.com \
--cc=15687@debbugs.gnu.org \
--cc=wgg2@member.fsf.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 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).