From bf7034048c16a95263e3f7c121dafbf1824ff28f Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 6 Jan 2024 13:45:33 +0200 Subject: [PATCH] ; * doc/emacs/custom.texi (Changing a Variable): Update example (bug#68279). --- doc/emacs/custom.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi index b45e0ef953d..4bd78f3ce83 100644 --- a/doc/emacs/custom.texi +++ b/doc/emacs/custom.texi @@ -188,14 +188,15 @@ find with @kbd{M-x customize-browse}. the customization buffer: @smallexample -[Hide] Kill Ring Max: 60 +[Hide] Kill Ring Max: Integer (positive or zero): 120 [State]: STANDARD. Maximum length of kill ring before oldest elements are thrown away. @end smallexample The first line shows that the variable is named @code{kill-ring-max}, formatted as @samp{Kill Ring Max} for easier -viewing. Its value is @samp{120}. The button labeled @samp{[Hide]}, +viewing, and also shows its expected type: a positive integer or zero. +The default value is @samp{120}. The button labeled @samp{[Hide]}, if activated, hides the variable's value and state; this is useful to avoid cluttering up the customization buffer with very long values (for this reason, variables that have very long values may start out -- 2.39.5