[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#68280: [PATCH] [doc/emacs/custom.texi] align value in example and de
From: |
Stefan Kangas |
Subject: |
bug#68280: [PATCH] [doc/emacs/custom.texi] align value in example and descriptions |
Date: |
Sat, 6 Jan 2024 03:42:41 -0800 |
Hiweed Mandriva3 <hiweedmandriva3@outlook.com> writes:
> [doc/emacs/custom.texi] align value in example and descriptions
> From 7f0647c480521ec461be81000b33b6a1814079d5 Mon Sep 17 00:00:00 2001
> From: Nerd <hiweedmandriva3@outlook.com>
> Date: Sat, 6 Jan 2024 13:20:25 +0800
> Subject: [PATCH] [doc/emacs/custom.texi] align value in example and
> descriptions
>
> ---
> doc/emacs/custom.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
> index 9c8558c..2f1b5b7 100644
> --- a/doc/emacs/custom.texi
> +++ b/doc/emacs/custom.texi
> @@ -195,7 +195,7 @@ Changing a Variable
>
> 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. Its value is @samp{60}. The button labeled @samp{[Hide]},
Thanks, but the new value in Emacs 29.1 is 120, so isn't it "Kill Ring
Max" that should be changed above, instead?
> 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.43.0