From 1a60ceaead6ca2b2e15a1bc758ed54d2a032c3e3 Mon Sep 17 00:00:00 2001 From: Nick Roberts Date: Mon, 18 Apr 2005 08:21:21 +0000 Subject: [PATCH] (Variable Definitions): Replace tooltip-mode example with save-place. --- lispref/customize.texi | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/lispref/customize.texi b/lispref/customize.texi index a1a61ab6b09..10911cea165 100644 --- a/lispref/customize.texi +++ b/lispref/customize.texi @@ -283,17 +283,14 @@ those other variables already have their intended values. operation of a certain feature. Assuming that the package is coded to check the value of the option, you still need to arrange for the package to be loaded. You can do that with @code{:require}. @xref{Common -Keywords}. Here is an example, from the library @file{tooltip.el}: +Keywords}. Here is an example, from the library @file{saveplace.el}: @example -(defcustom tooltip-mode nil - "Non-nil if Tooltip mode is enabled..." - :set (lambda (symbol value) - (tooltip-mode (or value 0))) - :initialize 'custom-initialize-default +(defcustom save-place nil + "*Non-nil means automatically save place in each file..." :type 'boolean - :require 'tooltip - :group 'tooltip) + :require 'saveplace + :group 'save-place) @end example If a customization item has a type such as @code{hook} or @code{alist}, -- 2.39.2