all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 15687@debbugs.gnu.org
Subject: bug#15687: 24.3.50; custom themes: disabling does not restore initial configuration
Date: Tue, 4 Nov 2014 19:48:09 -0800 (PST)	[thread overview]
Message-ID: <56f34eec-57e4-43e7-b601-99ea8850d6e1@default> (raw)
In-Reply-To: <cf8c4472-512e-4296-a7be-aa4f7b63fc08@default>

This bug should not have been renamed from "custom themes: disabling does not restore initial configuration" to "disabling custom theme does not reset vars".

It is *not about resetting variables*.  Not at all.

It is about restoring any number of settings that might have been changed (including customized using Customize) prior to enabling the custom theme: faces, frame parameters, etc. - as explained in this bug thread.

The point is that "disabling" a custom theme does not restore the pre-enabled state of everything that the theme changed.  Disabling only restores things relative to another custom theme.





  reply	other threads:[~2014-11-05  3:48 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56f34eec-57e4-43e7-b601-99ea8850d6e1@default \
    --to=drew.adams@oracle.com \
    --cc=15687@debbugs.gnu.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.