From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
Subject: Re: [PATCH] Add bp_location to Python interface
Date: Wed, 11 Jan 2012 10:27:00 -0000 [thread overview]
Message-ID: <E1RkvEJ-0001cT-Ck@fencepost.gnu.org> (raw)
In-Reply-To: <CAPftXULz7MiuBzdxDiQ1HPfyty+K2eW4xfUHNVv8cH77M-dKHg@mail.gmail.com> (message from Kevin Pouget on Wed, 11 Jan 2012 10:47:55 +0100)
> From: Kevin Pouget <kevin.pouget@gmail.com>
> Date: Wed, 11 Jan 2012 10:47:55 +0100
> Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
>
> >> +Return a tuple containing a sequence of @code{gdb.BpLocation} objects
> >> +(see below) associated with this breakpoint. Â A breakpoint with no location
> >> +is a pending breakpoint (@xref{Set Breaks, , pending breakpoints}).
> > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^^^^^
> > Still an @xref...
>
> sorry, I missed it in the first run ...
See below, it sounds like I totally failed to explain myself in this
matter.
> +@defun gdb.locations ()
> +Return a tuple containing a sequence of @code{gdb.BpLocation} objects
> +(see below) associated with this breakpoint. A breakpoint with no location
> +is a pending breakpoint (@xref{Set Breaks, , pending breakpoints}).
This @xref should become @pxref, because the cross reference is in
parentheses (that's the `p' part of `pxref') and is not a complete
sentence.
The other @xref that you changed to @pxref should be left alone.
> -become invisible to the user. @xref{Breakpoints In Python}, for further
> +become invisible to the user. @pxref{Breakpoints In Python}, for further
> details about this argument.
This should be @xref, as it is not in parentheses and is a complete
sentence.
Thanks, and sorry for my evidently unclear wording.
next prev parent reply other threads:[~2012-01-11 10:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 10:17 Kevin Pouget
2011-12-08 13:39 ` Phil Muldoon
2011-12-08 14:28 ` Kevin Pouget
2011-12-08 14:56 ` Phil Muldoon
2011-12-09 13:49 ` Kevin Pouget
2011-12-09 14:15 ` Phil Muldoon
2011-12-13 15:55 ` Kevin Pouget
2012-01-09 11:47 ` Kevin Pouget
2012-01-09 17:23 ` Eli Zaretskii
2012-01-10 15:09 ` Kevin Pouget
2012-01-10 16:03 ` Kevin Pouget
2012-01-10 17:25 ` Eli Zaretskii
2012-01-11 10:16 ` Kevin Pouget
2012-01-11 10:27 ` Eli Zaretskii [this message]
2012-01-10 22:24 ` Doug Evans
2012-01-11 9:05 ` Kevin Pouget
2012-01-11 19:45 ` Doug Evans
2012-01-27 13:04 ` Kevin Pouget
2012-03-30 19:51 ` Tom Tromey
2012-04-03 10:35 ` Kevin Pouget
2012-04-03 12:15 ` Phil Muldoon
2012-04-03 14:43 ` Paul_Koning
2012-04-04 8:36 ` Kevin Pouget
2012-05-09 7:18 ` Kevin Pouget
2012-04-05 16:27 ` Eli Zaretskii
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=E1RkvEJ-0001cT-Ck@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=pmuldoon@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