From: Eli Zaretskii <eliz@gnu.org>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: tromey@redhat.com, marc.khouzam@ericsson.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] util.c + doc [was Re: [RFC] Queries and frontends]
Date: Tue, 04 Aug 2009 17:51:00 -0000 [thread overview]
Message-ID: <83tz0no4d3.fsf@gnu.org> (raw)
In-Reply-To: <19064.2410.863604.37792@totara.tehura.co.nz>
> Date: Tue, 4 Aug 2009 22:11:54 +1200
> Cc: tromey@redhat.com, marc.khouzam@ericsson.com, gdb-patches@sourceware.org
> From: nickrob@snap.net.nz (Nick Roberts)
>
> > "value of `show confirm' command" sounds awkward (a command cannot
> > have a value). Can you suggest a better wording?
>
> Perhaps it's enough to say that they are disabled and point to the existing
> description.
> [...]
> + It also disables confirmation requests (@pxref{confirmation requests}).
Yes, that's good, but the sentence is too far from the first paragraph
of this section to make "It" self-explanatory. How about the variant
below?
The @code{server } prefix also disables confirmation requests
(@pxref{confirmation requests}).
next prev parent reply other threads:[~2009-08-04 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6D19CA8D71C89C43A057926FE0D4ADAA07C00023@ecamlmw720.eamcs.ericsson.se>
[not found] ` <19045.23703.743876.775308@totara.tehura.co.nz>
[not found] ` <m37hxwm3wr.fsf@fleche.redhat.com>
[not found] ` <19053.2107.342469.683795@totara.tehura.co.nz>
[not found] ` <m3iqheje2p.fsf@fleche.redhat.com>
[not found] ` <19054.23189.193878.534661@totara.tehura.co.nz>
[not found] ` <m3r5vztcpw.fsf@fleche.redhat.com>
2009-07-30 0:41 ` Nick Roberts
2009-07-30 0:42 ` Marc Khouzam
2009-07-30 7:24 ` Nick Roberts
2009-07-30 16:02 ` Marc Khouzam
2009-07-30 6:46 ` Eli Zaretskii
2009-08-04 10:12 ` Nick Roberts
2009-08-04 17:51 ` Eli Zaretskii [this message]
2009-08-06 5:21 ` Nick Roberts
2009-08-06 8:24 ` Andreas Schwab
2009-08-06 18:11 ` Eli Zaretskii
2009-08-04 16:32 ` [PATCH] util.c + doc 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=83tz0no4d3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=nickrob@snap.net.nz \
--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