From: Andreas Schwab <schwab@suse.de>
To: Matt <matt@excalamus.com>
Cc: 69745@debbugs.gnu.org
Subject: bug#69745: [PATCH] Fix incorrect Edebug docstrings
Date: Tue, 12 Mar 2024 13:59:58 +0100 [thread overview]
Message-ID: <mvmh6hbobap.fsf@suse.de> (raw)
In-Reply-To: <18e31efc662.110b51b75233014.2760074093528628525@excalamus.com> (matt@excalamus.com's message of "Tue, 12 Mar 2024 10:13:01 +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, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-03-12 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 9:13 bug#69745: [PATCH] Fix incorrect Edebug docstrings Matt
2024-03-12 12:59 ` Andreas Schwab [this message]
2024-03-15 17:22 ` Matt
2024-03-16 10:43 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvmh6hbobap.fsf@suse.de \
--to=schwab@suse.de \
--cc=69745@debbugs.gnu.org \
--cc=matt@excalamus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).