From c9c9756d21d19da8b7c265c1e9d6766e42ccfbfe Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 22 Sep 2018 10:54:58 +0300 Subject: [PATCH] Don't use obsolete variable 'save-place' in documentation * doc/lispref/customize.texi (Variable Definitions): Replace example of saveplace defcustom with a fictitious one, which will not bit-rot with time. (Bug#32741) --- doc/lispref/customize.texi | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/lispref/customize.texi b/doc/lispref/customize.texi index b3528b12d57..1cc7cb65b5f 100644 --- a/doc/lispref/customize.texi +++ b/doc/lispref/customize.texi @@ -449,15 +449,14 @@ those other variables already have their intended values. It is useful to specify the @code{:require} keyword for an option that turns on a certain feature. This causes Emacs to load the feature, if it is not already loaded, whenever the option is set. -@xref{Common Keywords}. Here is an example, from the library -@file{saveplace.el}: +@xref{Common Keywords}. Here is an example: @example -(defcustom save-place nil - "Non-nil means automatically save place in each file..." +(defcustom frobnicate-automatically nil + "Non-nil means automatically frobnicate all buffers." :type 'boolean - :require 'saveplace - :group 'save-place) + :require 'frobnicate-mode + :group 'frobnicate) @end example If a customization item has a type such as @code{hook} or -- 2.39.2