public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/15637] New: override a command from Python Date: Mon, 17 Jun 2013 14:03:00 -0000 [thread overview] Message-ID: <bug-15637-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15637 Bug ID: 15637 Summary: override a command from Python Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: tromey at redhat dot com Right now if you write a command in Python that has the same name as an existing command, there is no way to access the previous command. It would be handy if this were possible. I have a partial patch for this; I'll upload or push it a bit later. Now your command's invoke method can use the super 'invoke' to access the previous command. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-06-17 14:03 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-17 14:03 tromey at redhat dot com [this message] 2013-11-14 19:22 ` [Bug python/15637] " tromey at redhat dot com 2013-11-18 17:58 ` tromey at redhat dot com
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-15637-4717@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: 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).