From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb@sources.redhat.com
Subject: Re: $argc variable
Date: Tue, 08 Nov 2005 23:19:00 -0000 [thread overview]
Message-ID: <u7jbisp6n.fsf@gnu.org> (raw)
In-Reply-To: <43709E94.4070004@st.com> (message from Andrew STUBBS on Tue, 08 Nov 2005 12:48:20 +0000)
> Date: Tue, 08 Nov 2005 12:48:20 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: GDB List <gdb@sources.redhat.com>
Btw, Andrew, why do you post patches to gdb@sources.redhat.com, rather
than to gdb-patches@ ? The latter is the right place.
> In the documentation I changed a '@var' to '@code' because @var makes it
> upper case in the info and I thought that misleading.
Upper case is not the problem: makeinfo produces an uppercase word
from @var since time immemoriam, so anyone who's used to read Info
manuals is already used to that.
The problem here is that it's simply wrong to use @var in this case,
because $arg0 etc. are literal strings, to be used verbatim in the
actual script, not placeholders that stand for something else. So
your change is correct, although for the wrong reasons. ;-)
> -via @var{$arg0@dots{}$arg9}. A trivial example:
However, there _is_ something wrong here: the $ part should be outside
@var, since it's a literal character:
via @code{$@var{arg0}@dots{}$@var{arg9}}.
> +via @code{$arg0@dots{}$arg9}. A trivial example:
>
> @smallexample
> define adder
> print $arg0 + $arg1 + $arg2
> +end
> @end smallexample
In the example, I would suggest to use something other than arg0 etc.,
to avoid confusion with arg0..arg9 as placeholders in the paragraph
where you wanted to remove @var.
> +@kindex $argc
I'd replace this with "@cindex arguments for user-defined function".
Other than that, the documentation patch is okay with me. Thanks.
next prev parent reply other threads:[~2005-11-08 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 13:11 Andrew STUBBS
2005-11-03 19:51 ` Dan Nicolaescu
2005-11-07 0:18 ` Daniel Jacobowitz
2005-11-07 11:12 ` Andrew STUBBS
2005-11-07 13:35 ` Daniel Jacobowitz
2005-11-08 13:05 ` Andrew STUBBS
2005-11-08 23:19 ` Eli Zaretskii [this message]
2005-11-09 11:15 ` Andrew STUBBS
2005-11-09 19:19 ` Eli Zaretskii
2005-11-10 10:11 ` Andrew STUBBS
2005-11-13 17:35 ` Daniel Jacobowitz
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=u7jbisp6n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).