Delete description of deleted Customize functions

* doc/lispref/customize.texi (Variable Definitions): Remove the
description of 'custom-initialize-safe-set' and
'custom-initialize-safe-default', which were deleted in Emacs
23.2, and replace with the description of
'custom-initialize-delay'.
This commit is contained in:
Eli Zaretskii 2018-06-15 10:32:45 +03:00
parent fcd66d059c
commit 0b1a2ae84a

View file

@ -416,20 +416,14 @@ Use the @code{:set} function to initialize the variable, if it is
already set or has been customized; otherwise, just use already set or has been customized; otherwise, just use
@code{set-default}. @code{set-default}.
@item custom-initialize-safe-set @item custom-initialize-delay
@itemx custom-initialize-safe-default This functions behaves like @code{custom-initialize-set}, but it
These functions behave like @code{custom-initialize-set} delays the actual initialization to the next Emacs start. This should
(@code{custom-initialize-default}, respectively), but catch errors. be used in files that are preloaded (or for autoloaded variables), so
If an error occurs during initialization, they set the variable to that the initialization is done in the run-time context rather than
@code{nil} using @code{set-default}, and signal no error. the build-time context. This also has the side-effect that the
(delayed) initialization is performed with the @code{:set} function.
These functions are meant for options defined in pre-loaded files, @xref{Building Emacs}.
where the @var{standard} expression may signal an error because some
required variable or function is not yet defined. The value normally
gets updated in @file{startup.el}, ignoring the value computed by
@code{defcustom}. After startup, if one unsets the value and
reevaluates the @code{defcustom}, the @var{standard} expression can be
evaluated without error.
@end table @end table
@item :risky @var{value} @item :risky @var{value}