public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "plasmahh at gmx dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/28533] dont_repeat in gdb.Command doesn't have any effect anymore
Date: Wed, 05 Jan 2022 22:59:53 +0000	[thread overview]
Message-ID: <bug-28533-4717-wUqyyFrkfj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28533-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28533

--- Comment #2 from Dennis Lubert <plasmahh at gmx dot net> ---
Hm, intresting. After in the past there was a bug fixed I was under the
impression that this is a general "flag" to be set or similar in __init__.
Neither behaviour could be read from the documentation and I think this should
be changed, so this ticket is probably for that then.

It would be nice if the documentation then tells something about how and if it
interacts with any gdb.execute() invocations that themselves could invoke
dont_repeat indirectly. Or in other words if dont_repeat should be the last
thing bevore returning from invoke() or if it doesn't matter when it is called.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-01-05 22:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 14:16 [Bug python/28533] New: " plasmahh at gmx dot net
2022-01-05 14:17 ` [Bug python/28533] " ssbssa at sourceware dot org
2022-01-05 22:59 ` plasmahh at gmx dot net [this message]
2022-02-19 16:34 ` tromey at sourceware dot org
2022-06-15 20:00 ` cvs-commit at gcc dot gnu.org
2022-06-15 20:01 ` tromey at sourceware dot org

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=bug-28533-4717-wUqyyFrkfj@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).