Subject: bug#69745: [PATCH] Fix incorrect Edebug docstrings

From: Andreas Schwab <[email-masked]>
Date: Tue, 12 Mar 2024 13:59:58 +0100

On Mär 12 2024, Matt wrote:

> When edebug-print-length and edebug-print-level are nil, they default to print-level and print-length.  The docstrings currently say the opposite, that edebug defaults to the print variables if non-nil.

That's not correct.  The edebug-print-* variables, when non-nil,
override the corresponding print-* variables during printing (see
edebug-safe-prin1-to-string).  When they are nil, they have no effect.

>  (defcustom edebug-print-length 50
> -  "If non-nil, default value of `print-length' for printing results in Edebug."
> +  "If nil, default value of `print-length' is used for printing results in Edebug."

That fails to say what happens if it is non-nil, which is the actual
relevant information.

-- 
Andreas Schwab, SUSE Labs, [email-masked]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."