From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: add doc for "set/show debug event-loop"
Date: Sat, 03 Oct 2020 11:29:51 +0300 [thread overview]
Message-ID: <83zh53g1a8.fsf@gnu.org> (raw)
In-Reply-To: <20201003001437.3066505-2-simon.marchi@polymtl.ca> (message from Simon Marchi via Gdb-patches on Fri, 2 Oct 2020 20:14:37 -0400)
> Date: Fri, 2 Oct 2020 20:14:37 -0400
> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
>
> I forgot that "set/show debug" commands are listed in the doc and in
> NEWS, so here they are.
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Debugging Output): Add set/show debug event-loop.
>
> gdb/ChangeLog:
>
> * NEWS: Mention set/show debug event-loop.
Thanks.
> +@item set debug event-loop
> +@cindex event-loop debugging
> +Controls output of debugging info about the event loop. The possible
> +values are off, all (shows all debugging info) and all-except-ui (shows
I think the values should be in @samp, otherwise they look like plain
words, and the sentence is confusing then.
> +@item show debug event-loop
> +Displays the current state of displaying debugging info about the event
^^^^^^^^
"Shows" will read better here, since "Displays the state of
displaying" reuses the same word.
OK with those fixed.
next prev parent reply other threads:[~2020-10-03 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 0:14 [PATCH 1/2] gdb/doc: space out list entries, fix one type Simon Marchi via Gdb-patches
2020-10-03 0:14 ` [PATCH 2/2] gdb: add doc for "set/show debug event-loop" Simon Marchi via Gdb-patches
2020-10-03 8:29 ` Eli Zaretskii via Gdb-patches [this message]
2020-10-04 16:41 ` Simon Marchi via Gdb-patches
2020-10-04 16:50 ` Eli Zaretskii via Gdb-patches
2020-10-03 8:30 ` [PATCH 1/2] gdb/doc: space out list entries, fix one type Eli Zaretskii via Gdb-patches
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=83zh53g1a8.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=simon.marchi@polymtl.ca \
/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