unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: obsolete comment in tool-bar.el
Date: Sun, 10 Jul 2005 22:21:42 -0500 (CDT)	[thread overview]
Message-ID: <200507110321.j6B3LgG09526@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1DrUE7-0004ob-G4@fencepost.gnu.org> (rms@gnu.org)

This concerns the documentation for the two new :initialize functions.
They are kind of internal and hence I believe that maybe they do not
need to be mentioned in the already very long NEWS.  On the other
hand, maybe it might be useful to mention them in the Elisp manual,
for instance because people experimenting with changing the defcustoms
in question need to be aware of their subtleties.

The patch below documents them.  The small unrelated change in the
patch appears necessary regardless.

===File ~/customize.texi-diff===============================
*** customize.texi	18 Jun 2005 08:44:38 -0500	1.45
--- customize.texi	10 Jul 2005 21:52:01 -0500	
***************
*** 270,275 ****
--- 270,290 ----
  Use the @code{:set} function to initialize the variable, if it is
  already set or has been customized; otherwise, just use
  @code{set-default}.
+ 
+ @item custom-initialize-safe-set
+ @itemx custom-initialize-safe-default
+ These functions behave like @code{custom-initialize-set}
+ (@code{custom-initialize-default}, respectively), but catch errors.
+ If an error occurs during initialization, they set the variable to
+ @code{nil} using @code{set-default}, and throw no error.
+ 
+ These two functions are only meant for options defined in pre-loaded
+ files, where some variables or functions used to compute the option's
+ value may not yet be defined.  The option normally gets updated in
+ @file{startup.el}, ignoring the previously computed value.  Because of
+ this typical usage, the value which these two functions compute
+ normally only matters when, after startup, one unsets the option's
+ value and then reevaluates the defcustom.
  @end table
  
  @item :set-after @var{variables}
***************
*** 318,325 ****
  Internally, @code{defcustom} uses the symbol property
  @code{standard-value} to record the expression for the default value,
  and @code{saved-value} to record the value saved by the user with the
! customization buffer.  The @code{saved-value} property is actually a
! list whose car is an expression which evaluates to the value.
  
  @node Customization Types
  @section Customization Types
--- 333,340 ----
  Internally, @code{defcustom} uses the symbol property
  @code{standard-value} to record the expression for the default value,
  and @code{saved-value} to record the value saved by the user with the
! customization buffer.  Both properties are actually lists whose car is
! an expression which evaluates to the value.
  
  @node Customization Types
  @section Customization Types
============================================================

  reply	other threads:[~2005-07-11  3:21 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 12:40 obsolete comment in tool-bar.el Mathias Dahl
2005-07-07 19:15 ` Luc Teirlinck
2005-07-08  6:40   ` Mathias Dahl
2005-07-08 15:29     ` Luc Teirlinck
2005-07-08 17:40   ` Richard M. Stallman
2005-07-08 18:53     ` Drew Adams
2005-07-09  1:53       ` Luc Teirlinck
2005-07-09  4:20       ` Richard M. Stallman
2005-07-09  2:35     ` Luc Teirlinck
2005-07-10  5:19       ` Richard M. Stallman
2005-07-11  3:21         ` Luc Teirlinck [this message]
2005-07-11 16:53           ` Richard M. Stallman
2005-07-11 17:56             ` David Kastrup
2005-07-11 20:28               ` Luc Teirlinck
2005-07-12  3:20               ` Richard M. Stallman
2005-07-13  3:02                 ` Luc Teirlinck
2005-07-13 16:52                   ` Richard M. Stallman
2005-07-14  2:08                     ` Luc Teirlinck
2005-07-14  8:14                       ` YAMAMOTO Mitsuharu
2005-07-14 16:50                         ` Luc Teirlinck
2005-07-14 18:30                         ` Luc Teirlinck
2005-07-15  4:35                           ` Stefan Monnier
2005-07-15 13:53                             ` Luc Teirlinck
2005-07-15 20:44                               ` Stefan Monnier
2005-07-15 22:05                                 ` Luc Teirlinck
2005-07-15 22:46                                 ` Luc Teirlinck
2005-07-16  1:47                                 ` Luc Teirlinck
2005-07-16  2:04                                 ` Luc Teirlinck
2005-07-19  2:59                                   ` Luc Teirlinck
2005-07-19 14:41                                     ` Stefan Monnier
2005-07-20  4:05                                       ` Luc Teirlinck
2005-07-21  5:40                                         ` Stefan Monnier
2005-07-20  8:34                                     ` Richard M. Stallman
     [not found]                       ` <E1Dt8bd-0001fH-Eu@fencepost.gnu.org>
2005-07-14 22:05                         ` Luc Teirlinck
2005-07-15  3:24                           ` Luc Teirlinck
2005-07-15 18:10                             ` Richard M. Stallman
2005-07-16  2:32                               ` Luc Teirlinck
2005-07-13  3:20                 ` Luc Teirlinck
2005-07-09  3:57     ` Luc Teirlinck
2005-07-09  7:55       ` Eli Zaretskii
2005-07-09 13:57         ` Luc Teirlinck
2005-07-12  4:13           ` YAMAMOTO Mitsuharu
2005-07-12 12:20             ` YAMAMOTO Mitsuharu
2005-07-12 18:25               ` Luc Teirlinck
2005-07-12 23:58                 ` Luc Teirlinck
2005-07-13 16:52                   ` Richard M. Stallman
2005-07-12 20:19               ` Luc Teirlinck
2005-07-13  1:53               ` Luc Teirlinck

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=200507110321.j6B3LgG09526@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).