From: Eli Zaretskii <eliz@gnu.org>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [python] [patch] set/show extended-prompt
Date: Thu, 11 Aug 2011 16:21:00 -0000 [thread overview]
Message-ID: <83d3gbyl5j.fsf@gnu.org> (raw)
In-Reply-To: <m3liv0yol6.fsf@redhat.com>
> From: Phil Muldoon <pmuldoon@redhat.com>
> Date: Thu, 11 Aug 2011 16:06:45 +0100
>
>
> This patch adds extended-prompt capabilities to GDB. In addition it
> adds a prompt substitution library. I made the extended-prompt lazily
> control the prompt_hook on setting, over controlling it unconditionally. The
> rest of the function remains the same other than in-Python documentation
> as was found in Archer.
Thanks, I have a few comments about the documentation part:
> +@xref{gdb.prompt} for a list of the flags that can be used for
^
If you run "make info", it will complain here, because you need to add
a comma after the right brace.
> + The prompt is updated with the value of the
> +flags each time it is displayed.
Is "flags" a good term? I think "escape sequence" is better, e.g.:
Any escape sequences specified as part of the prompt string are
replaced with the corresponding strings each time the prompt is
displayed.
> +Note that when an extended-prompt is set, it takes control of the
> +@var{prompt_hook} hook. @xref{prompt_hook} for further information.
^
Likewise, you need a comma here.
> +@item show extended-prompt
> +Prints the extended prompt. Each time the prompt is displayed, it is
> +updated with the current value of the flags passed to it with ``set
> +extended-prompt''.
@code{set extended-prompt}. And the same comment about "flags"
applies here as well.
> +@smallexample
> +substitute_prompt (``frame: \f, print arguments: \p@{print frame-arguments@}'')
> +@end smallexample
The line inside @example should be broken into two, as it is too long.
> +will return the string:
This line needs an @exdent before it, because it is not a new
paragraph.
> +@smallexample
> +``frame: main, print arguments: scalars''
> +@end smallexample
Aren't these ``..'' quotes left verbatim in the printed version of the
manual? I think you need literal ".." quotes here, since they are not
converted inside @smallexample.
next prev parent reply other threads:[~2011-08-11 16:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 15:07 Phil Muldoon
2011-08-11 16:21 ` Eli Zaretskii [this message]
2011-08-11 18:01 ` Phil Muldoon
2011-08-11 18:22 ` Eli Zaretskii
2011-08-11 21:42 ` Matt Rice
2011-08-12 14:51 ` Phil Muldoon
2011-08-12 15:40 ` Phil Muldoon
2011-08-12 20:22 ` Tom Tromey
2011-08-12 22:20 ` Phil Muldoon
2011-08-13 6:27 ` Eli Zaretskii
2011-08-15 14:03 ` Phil Muldoon
2011-08-15 16:58 ` Eli Zaretskii
2011-08-16 11:22 ` Phil Muldoon
2011-08-16 13:39 ` Eli Zaretskii
2011-08-17 11:02 ` Phil Muldoon
2011-08-15 17:51 ` Tom Tromey
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=83d3gbyl5j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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