From: "Richard M. Stallman" <rms@gnu.org>
Cc: abraham@dina.kvl.dk, emacs-devel@gnu.org
Subject: Re: custom-declare-variable
Date: Mon, 11 Jul 2005 12:53:34 -0400 [thread overview]
Message-ID: <E1Ds1XC-0008Jj-UO@fencepost.gnu.org> (raw)
In-Reply-To: <200507042320.j64NKNe15629@raven.dms.auburn.edu> (message from Luc Teirlinck on Mon, 4 Jul 2005 18:20:23 -0500 (CDT))
First of all, the docstring appears to contain a falsehood. From the
comment (and from the actual code), it appears that DEFAULT is not
_currently_ stored in the standard theme. But the docstring clearly
seems to indicate an intent to store it in the standard theme and make
standard-value obsolete, which according to the comment, requires a
rewrite of defvar and various other primitives.
This seems to be completely crazy. There would not appear to be
anything wrong with standard-value.
I agree. I think it would be best to eliminate the `standard' theme
(which currently would normally be empty) and stick with the idea
that all enabled themes override the standard values.
If not, should
we not delete the above comment and remove the (apparently) false
claims from the above second paragraph of the docstring:
DEFAULT is stored in SYMBOL's property `standard-value'. At the
same time, SYMBOL's property `force-value' is set to nil, as the value
is no longer rogue.
I did that (more or less). Thanks.
prev parent reply other threads:[~2005-07-11 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 23:20 custom-declare-variable Luc Teirlinck
2005-07-04 23:37 ` custom-declare-variable Luc Teirlinck
2005-07-05 9:37 ` custom-declare-variable Per Abrahamsen
2005-07-05 10:54 ` custom-declare-variable Kim F. Storm
2005-07-06 1:34 ` custom-declare-variable Luc Teirlinck
2005-07-06 17:55 ` custom-declare-variable Richard M. Stallman
2005-07-05 23:55 ` custom-declare-variable Luc Teirlinck
2005-07-11 16:53 ` Richard M. Stallman [this message]
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=E1Ds1XC-0008Jj-UO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=abraham@dina.kvl.dk \
--cc=emacs-devel@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 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).