Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 1/2] Fix gdb.flush documentation
Date: Mon, 15 Aug 2022 12:50:08 -0600	[thread overview]
Message-ID: <20220815185009.1288079-2-tromey@adacore.com> (raw)
In-Reply-To: <20220815185009.1288079-1-tromey@adacore.com>

The gdb.flush documentation does not mention the 'stream' argument in
the function signature, only in the description.  This patch fixes the
oversight.
---
 gdb/doc/python.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 9a823409854..7aa9e853d85 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -511,7 +511,7 @@ relevant stream.
 @end defun
 
 @findex gdb.flush
-@defun gdb.flush ()
+@defun gdb.flush (@r{[}, stream@r{]})
 Flush the buffer of a @value{GDBN} paginated stream so that the
 contents are displayed immediately.  @value{GDBN} will flush the
 contents of a stream automatically when it encounters a newline in the
-- 
2.34.1


  reply	other threads:[~2022-08-15 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 18:50 [PATCH 0/2] Fix two small Python flush problems Tom Tromey via Gdb-patches
2022-08-15 18:50 ` Tom Tromey via Gdb-patches [this message]
2022-08-15 19:00   ` [PATCH 1/2] Fix gdb.flush documentation Eli Zaretskii via Gdb-patches
2022-08-15 18:50 ` [PATCH 2/2] Fix flush for sys.stderr Tom Tromey via Gdb-patches
2022-08-30 17:49 ` [PATCH 0/2] Fix two small Python flush problems Tom Tromey 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=20220815185009.1288079-2-tromey@adacore.com \
    --to=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox