From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb/python: improve formatting of help text for user defined commands
Date: Tue, 17 May 2022 15:19:21 +0300 [thread overview]
Message-ID: <83sfp8gxme.fsf@gnu.org> (raw)
In-Reply-To: <58a7e3085365af2ac05409b78f6d15bf5240cd2c.1652784658.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Tue, 17 May 2022 11:51:45 +0100)
> Date: Tue, 17 May 2022 11:51:45 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Andrew Burgess <aburgess@redhat.com>
>
> +* Python API
> +
> + ** GDB will now reformat the doc string for gdb.Command and
> + gdb.Parameter sub-classes to remove unnecessary whitespace before
> + using the string as the help output.
AFAIU, the feature doesn't remove "unnecessary whitespace", it removes
"unnecessary indentation", or if you want to be more accurate "removes
unnecessary leading whitespace from each line".
Thanks.
next prev parent reply other threads:[~2022-05-17 12:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:51 [PATCH 0/2] Improve help test for commands defined in Python Andrew Burgess
2022-05-17 10:51 ` [PATCH 1/2] gdb: use gdb::unique_xmalloc_ptr<char> for docs in cmdpy_init Andrew Burgess
2022-05-26 17:43 ` Tom Tromey
2022-05-28 10:10 ` Andrew Burgess
2022-05-17 10:51 ` [PATCH 2/2] gdb/python: improve formatting of help text for user defined commands Andrew Burgess
2022-05-17 12:19 ` Eli Zaretskii [this message]
2022-05-17 22:41 ` Lancelot SIX
2022-05-18 10:19 ` Andrew Burgess
2022-05-18 12:09 ` Eli Zaretskii
2022-05-26 17:46 ` Tom Tromey
2022-05-28 10:11 ` Andrew Burgess
2022-05-31 21:54 ` Carl Love
2022-05-31 23:10 ` Carl Love
2022-06-03 18:05 ` Carl Love
2022-06-06 11:40 ` [PUSHED] gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp Andrew Burgess
2022-06-07 16:08 ` Carl Love
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sfp8gxme.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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.
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).