[Emacs-diffs] Changes to emacs/lispref/customize.texi

[Luc Teirlinck]

Index: emacs/lispref/customize.texi
diff -c emacs/lispref/customize.texi:1.45 emacs/lispref/customize.texi:1.46
*** emacs/lispref/customize.texi:1.45   Sat Jun 18 13:42:31 2005
--- emacs/lispref/customize.texi        Thu Jul 14 01:07:23 2005
***************
*** 12,18 ****
  definitions---as well as face definitions (@pxref{Defining Faces}).
  
  @menu
! * Common Keywords::      Common keyword arguments for all kinds of 
                             customization declarations.
  * Group Definitions::    Writing customization group definitions.
  * Variable Definitions:: Declaring user options.
--- 12,18 ----
  definitions---as well as face definitions (@pxref{Defining Faces}).
  
  @menu
! * Common Keywords::      Common keyword arguments for all kinds of
                             customization declarations.
  * Group Definitions::    Writing customization group definitions.
  * Variable Definitions:: Declaring user options.
***************
*** 270,275 ****
--- 270,291 ----
  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.  By that time, the necessary
+ variables and functions will be defined, so there will not be an error.
  @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
--- 334,341 ----
  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
***************
*** 1088,1095 ****
  argument with the same syntax as the keyword argument to
  @code{defcustom} with the same name.  The third argument is a
  documentation string for the new widget.  You will be able to see that
! string with the @kbd{M-x widget-browse @key{ret} binary-tree-of-string
! @key{ret}} command.
  
  After these mandatory arguments follow the keyword arguments.  The most
  important is @code{:type}, which describes the data type we want to match
--- 1104,1111 ----
  argument with the same syntax as the keyword argument to
  @code{defcustom} with the same name.  The third argument is a
  documentation string for the new widget.  You will be able to see that
! string with the @kbd{M-x widget-browse @key{RET} binary-tree-of-string
! @key{RET}} command.
  
  After these mandatory arguments follow the keyword arguments.  The most
  important is @code{:type}, which describes the data type we want to match