From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: emacs-devel@gnu.org, jeff.dwork@amd.com
Subject: Re: [jeff.dwork@amd.com: Re: customize]
Date: Mon, 16 Sep 2002 18:01:41 +0200 [thread overview]
Message-ID: <rjhegp9b4q.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: <E17qxcL-0003pv-00@fencepost.gnu.org> (Richard Stallman's message of "Mon, 16 Sep 2002 11:16:53 -0400")
Richard Stallman <rms@gnu.org> writes:
> I looked at this message, and then studied custom-save-delete.
> It looks like the reason for this behavior is that custom-save-delete
> only deletes calls to custom-save-variables at top level in the file.
Yes.
> Should we try to make it find and delete calls that are inside other
> constructs?
No.
However, I believe it would be useful to make custom-save-variables
signal an error if it is called from other places than the top-level.
If that is possible.
> To make that reliable, we would need to prevent it from
> deleting instances of `custom-save-variables' inside strings, or lists
> that have that symbol as car but are not expressions.
The problem is that Jeff's code is just a special case of the more
common:
(if (< emacs-major-version 21)
;; Emacs 20 customization.
(custom-save-variables ...)
;; Emacs 21 customization.
(custom-save-variables ...))
Which is impossible to make robust. What we should encourage people
who need such functionality to do instead, is
(if (< emacs-major-version 21)
;; Emacs 20 customization.
(setq custom-file "~/.custom-20.el")
;; Emacs 21 customization.
(setq custom-file "~/.custom-21.el"))
(load-file custom-file)
prev parent reply other threads:[~2002-09-16 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 15:16 [jeff.dwork@amd.com: Re: customize] Richard Stallman
2002-09-16 16:01 ` Per Abrahamsen
2002-09-16 16:01 ` Per Abrahamsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rjhegp9b4q.fsf@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=emacs-devel@gnu.org \
--cc=jeff.dwork@amd.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 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.