public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/17291] IWBN if the print format was available to pretty-printers.
Date: Fri, 15 Jul 2022 15:28:53 +0000	[thread overview]
Message-ID: <bug-17291-4717-kqDX8CKNGJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17291-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c4a3dbaf1132105586586617a59d0e7566eefd41

commit c4a3dbaf1132105586586617a59d0e7566eefd41
Author: Tom Tromey <tromey@adacore.com>
Date:   Mon Jun 6 09:54:45 2022 -0600

    Expose current 'print' settings to Python

    PR python/17291 asks for access to the current print options.  While I
    think this need is largely satisfied by the existence of
    Value.format_string, it seemed to me that a bit more could be done.

    First, while Value.format_string uses the user's settings, it does not
    react to temporary settings such as "print/x".  This patch changes
    this.

    Second, there is no good way to examine the current settings (in
    particular the temporary ones in effect for just a single "print").
    This patch adds this as well.

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

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

  parent reply	other threads:[~2022-07-15 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 16:33 [Bug python/17291] New: " dje at google dot com
2022-06-05 16:19 ` [Bug python/17291] " tromey at sourceware dot org
2022-06-07 15:29 ` tromey at sourceware dot org
2022-07-15 15:28 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-15 15:29 ` tromey at sourceware dot org
2022-08-30  2:28 ` shihyente at hotmail dot com
2023-07-21  7:55 ` shihyente at hotmail dot com
2023-07-21 12:22 ` tromey at sourceware dot org
2023-07-21 14:14 ` shihyente at hotmail 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-17291-4717-kqDX8CKNGJ@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).