From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New substitute-path commands
Date: Mon, 10 Jul 2006 19:53:00 -0000 [thread overview]
Message-ID: <ud5cdnsml.fsf@gnu.org> (raw)
In-Reply-To: <20060710054027.GF971@adacore.com> (message from Joel Brobecker on Sun, 9 Jul 2006 22:40:27 -0700)
> Date: Sun, 9 Jul 2006 22:40:27 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sources.redhat.com
>
> > I suggested to have this text after the command description. In that
> > context, @var{from} and @var{to} refer to the command's arguments.
> > But you moved the description higher in the text, which made those
> > reference dangling. So this needs to be reworded in some way.
>
> You're right. It didn't work that way at all. You'll see my attempt
> at fixing it in this version of the patch.
This version is okay to go in, provided that you fix these small
gotchas:
> +In the @ref{set substitute-path} command description, these two
> +parts are named respectively @var{from} and @var{to}. @value{GDBN}
@ref needs some punctuation after the closing brace (makeinfo should
have griped about that). In addition, @ref produces something like
"Section X.YZ [Foo Bar]" in the printed version of the manual, so this
sentence will look awkwardly non-English there ("In the Section X.YZ
[Source Path], p.123 command description, these two...").
So please reword, e.g. like this:
In @ref{set substitute-path}, we name these two parts @var{from} and
@var{to}, respectively ...
> To define a source path
> +substitution rule, use the @ref{set substitute-path} command.
Such usage of @ref produces bad results, for the 2nd reason mentioned
above. You should use @pxref here:
To define a source path substitution rule, use the @code{set
substitute-path} command (@pxref{set substitute-path}).
next prev parent reply other threads:[~2006-07-10 19:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 21:58 Joel Brobecker
2006-07-05 22:49 ` Andreas Schwab
2006-07-05 23:01 ` Daniel Jacobowitz
2006-07-06 4:47 ` Joel Brobecker
2006-07-06 16:07 ` PAUL GILLIAM
2006-07-06 16:30 ` Daniel Jacobowitz
2006-07-06 21:28 ` Joel Brobecker
2006-07-07 5:22 ` Joel Brobecker
2006-07-07 9:40 ` Eli Zaretskii
2006-07-07 19:12 ` Joel Brobecker
2006-07-08 12:19 ` Eli Zaretskii
2006-07-10 5:40 ` Joel Brobecker
2006-07-10 19:53 ` Eli Zaretskii [this message]
2006-07-10 21:47 ` Joel Brobecker
2006-07-10 21:51 ` Daniel Jacobowitz
2006-07-10 21:56 ` Joel Brobecker
2006-07-10 21:58 ` Daniel Jacobowitz
2006-07-11 3:24 ` Eli Zaretskii
2006-07-07 10:39 ` Andrew STUBBS
2006-07-07 16:12 ` Joel Brobecker
2006-07-07 16:45 ` Andrew STUBBS
2006-07-07 17:20 ` Joel Brobecker
2006-07-11 12:47 ` Daniel Jacobowitz
2006-07-11 20:30 ` Joel Brobecker
2006-07-11 20:33 ` Daniel Jacobowitz
2006-07-11 20:45 ` Joel Brobecker
2006-07-11 22:25 ` Joel Brobecker
2006-07-11 22:31 ` Christopher Faylor
2006-07-11 22:50 ` Daniel Jacobowitz
2006-07-11 23:00 ` Joel Brobecker
2006-07-12 3:22 ` Eli Zaretskii
2006-07-12 3:47 ` Daniel Jacobowitz
2006-07-12 4:50 ` Joel Brobecker
2006-07-12 14:09 ` Daniel Jacobowitz
2006-07-06 3:31 ` Eli Zaretskii
2006-07-06 4:46 ` Joel Brobecker
2006-07-06 9:36 ` Andrew STUBBS
2006-07-06 21:19 ` Jason Molenda
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=ud5cdnsml.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.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