public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Add to documentation of Python 'dont_repeat' method Date: Wed, 15 Jun 2022 20:00:55 +0000 (GMT) [thread overview] Message-ID: <20220615200055.E440F3858D32@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=285dfa0f6877ea7677e84c3c1001c5d339fbbe5e commit 285dfa0f6877ea7677e84c3c1001c5d339fbbe5e Author: Tom Tromey <tom@tromey.com> Date: Sat Feb 19 09:33:12 2022 -0700 Add to documentation of Python 'dont_repeat' method PR python/28533 points out that the Python 'dont_repeat' documentation is a bit ambiguous about when the method ought to be called. This patch spells it out. Diff: --- gdb/doc/python.texi | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi index 75804ef975e..62db5f27016 100644 --- a/gdb/doc/python.texi +++ b/gdb/doc/python.texi @@ -4001,8 +4001,10 @@ not documented.'' is used. @defun Command.dont_repeat () By default, a @value{GDBN} command is repeated when the user enters a blank line at the command prompt. A command can suppress this -behavior by invoking the @code{dont_repeat} method. This is similar -to the user command @code{dont-repeat}, see @ref{Define, dont-repeat}. +behavior by invoking the @code{dont_repeat} method at some point in +its @code{invoke} method (normally this is done early in case of +exception). This is similar to the user command @code{dont-repeat}, +see @ref{Define, dont-repeat}. @end defun @defun Command.invoke (argument, from_tty)
reply other threads:[~2022-06-15 20:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220615200055.E440F3858D32@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).