From: Eli Zaretskii <eliz@gnu.org>
To: pmuldoon@redhat.com
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] PR python/12438
Date: Thu, 07 Jul 2011 18:47:00 -0000 [thread overview]
Message-ID: <83y60ang8j.fsf@gnu.org> (raw)
In-Reply-To: <m3liwarryf.fsf@redhat.com>
> From: Phil Muldoon <pmuldoon@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 07 Jul 2011 17:11:36 +0100
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -20801,10 +20801,16 @@ End with a line saying just "end".
>
> @kindex maint set python print-stack
> @item maint set python print-stack
> -By default, @value{GDBN} will print a stack trace when an error occurs
> -in a Python script. This can be controlled using @code{maint set
> -python print-stack}: if @code{on}, the default, then Python stack
> -printing is enabled; if @code{off}, then Python stack printing is
> +This command is now deprecated. Instead use @code{set python
> +print-stack} (@pxref{set python print-stack}).
> +
> +@kindex set python print-stack
> +@item set python print-stack
> +@anchor{set python print-stack}
> +By default, @value{GDBN} will not print a stack trace when an error
> +occurs in a Python script. This can be controlled using @code{set
> +python print-stack}: if @code{on}, then Python stack printing is
> +enabled; if @code{off}, the default, then Python stack printing is
> disabled.
> @end table
Thanks. This part is okay, but please lose the @pxref and the anchor,
because the referenced part is just one line away. Instead, say
something like "..., described below."
next prev parent reply other threads:[~2011-07-07 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 9:38 Phil Muldoon
2011-06-30 19:58 ` Tom Tromey
2011-07-07 16:16 ` Phil Muldoon
2011-07-07 18:47 ` Eli Zaretskii [this message]
2011-07-07 18:52 ` Tom Tromey
2011-07-11 17:16 ` Phil Muldoon
2011-10-17 13:00 ` Kevin Pouget
2011-10-17 13:49 ` Phil Muldoon
2011-10-19 20:56 ` Tom Tromey
2011-10-20 12:33 ` Phil Muldoon
2011-10-21 9:43 ` Kevin Pouget
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=83y60ang8j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@redhat.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