unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Hilary J Holz <hilary@hholz.com>
Cc: 12582@debbugs.gnu.org
Subject: bug#12582: 24.1.50; customize settings not persisting across sessions + CHANGED outside Customize flag issue
Date: Fri, 05 Oct 2012 18:16:13 -0400	[thread overview]
Message-ID: <clfw5stviq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <C5BE8596-CE7F-4ADF-89E6-4B806CE7732D@hholz.com> (Hilary J. Holz's message of "Fri, 5 Oct 2012 15:06:19 -0700")

Hilary J Holz wrote:

> I would have done that if the problem had been local to the package.
> However, there remains the issue with CHANGED outside Customize.

The problem is local to the package if it only occurs with variables
from that package. Can you demonstrate this problem with any standard
Emacs custom option?

It's trivial to make such a bug occur. Eg:

(defvar shell-switcher-new-shell-function 57)

(defcustom shell-switcher-new-shell-function 'shell-switcher-make-eshell
  "..."
  :group 'shell-switcher)

Evaluating that will give a "CHANGED outside Customize." message.

OK, that's an artificial example, but similar things can easily happen
for example with packages split into multiple source files that
accidentally define variables more than once. It's a bug in the package,
not in Custom.





  reply	other threads:[~2012-10-05 22:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 21:31 bug#12582: 24.1.50; customize settings not persisting across sessions + CHANGED outside Customize flag issue Hilary J Holz
2012-10-05 21:46 ` Glenn Morris
2012-10-05 21:54   ` Glenn Morris
2012-10-05 22:18     ` Hilary J Holz
2012-10-12  1:06     ` Glenn Morris
2012-10-05 22:06   ` Hilary J Holz
2012-10-05 22:16     ` Glenn Morris [this message]
2012-10-05 22:26       ` Hilary J Holz
2012-10-05 22:17 ` Stefan Monnier
2012-10-05 22:24   ` Hilary J Holz

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=clfw5stviq.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=12582@debbugs.gnu.org \
    --cc=hilary@hholz.com \
    /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).