From: "Roland Winkler" <winkler@gnu.org>
To: 13699@debbugs.gnu.org
Subject: bug#13699: 24.2.93; multiple defcustoms for one variable
Date: Tue, 12 Feb 2013 13:57:01 -0600 [thread overview]
Message-ID: <87a9r9s3ua.fsf@lukas.physics.niu.edu> (raw)
start emacs -Q
load the following two files (first bar.el, then baz.el)
cat > bar.el <<EOF
(defcustom foo 'bar
"This is bar.el.")
EOF
cat > baz.el <<EOF
(defcustom foo 'baz
"This is baz.el.")
EOF
Expected result:
Either loading baz.el overrides completely loading bar.el,
so that C-h v foo reflects baz.el only.
Or emacs "remembers" bar.el so that C-h foo indicates the fact that
foo was first defined in bar.el and foo kept its value defined there.
Actual result:
C-h v foo says
foo is a variable defined in `baz.el'.
Its value is bar
Original value was baz
Documentation:
This is baz.el.
The actual value of foo is the original value from bar.el,
but "Original value was baz" denies the fact that this value
stems from bar.el.
I noticed this problem with the variable mail-signature which
sendmail.el initializes with a value of t. But my old version of vm
also initialized it with a value of nil. With sendmail.el being
loaded before vm, I got the value of t, but it took me a little
while to figure out how this value came about.
I suggest that multiple calls of defcustom appearing for the same
variable in different files should be handled consistently so that
it becomes possible to trace back how the value of the variable
came about.
In GNU Emacs 24.2.93.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.12.9)
of 2013-02-08 on lukas
Windowing system distributor `The X.Org Foundation', version 11.0.10706000
System Description: Ubuntu 8.04.4 LTS
next reply other threads:[~2013-02-12 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 19:57 Roland Winkler [this message]
2013-02-12 23:10 ` bug#13699: 24.2.93; multiple defcustoms for one variable Glenn Morris
2013-02-12 23:23 ` Roland Winkler
2013-02-12 23:54 ` Glenn Morris
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=87a9r9s3ua.fsf@lukas.physics.niu.edu \
--to=winkler@gnu.org \
--cc=13699@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.