From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: MI handshaking
Date: Sat, 06 Nov 2004 10:12:00 -0000 [thread overview]
Message-ID: <01c4c3e8$Blat.v2.2.2$853fdac0@zahav.net.il> (raw)
In-Reply-To: <20041105221222.GC8318@white> (message from Bob Rossi on Fri, 5 Nov 2004 17:12:22 -0500)
> Date: Fri, 5 Nov 2004 17:12:22 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb-patches@sources.redhat.com
>
> I really am not good at editing info files but am trying to do my
> best to help out.
You are doing a good job, although I have a few more minor comments,
see below.
The @cindex lines are collected by the program that generates the Info
files and put into the "Index" node. Thereafter, you can use the `i'
command in the Info readers to quickly find stuff in the manual; that
command works by searching the string you type in the index. This is
the most efficient means of using the manual as a reference, when you
know something is in the manual and need a fast way of finding it.
If you want to learn more about Texinfo, I suggest to read the manual
that comes with the Texinfo package.
> +@item
> +For more information on handshaking see @ref{GDB/MI Handshaking Interface}
> +@end itemize
Don't make this an @item (just a simple sentence that goes after @end
itemize), and make sure there's a period or comma after the closing
brace of @ref{...}.
> +However, if @value{GDBN} is started with the -i=mi flag, then this tells
The "-i=mi" part should be in @samp{}.
> +untested protocols, they could simply try to invoke @value{GDBN} with
> +-i=mi@var{N}, where @var{N} is version they wish to communicate with.
Same here. And please don't use caps inside @var{}, as they look ugly
in print.
> +@cindex @dfn{stable MI protocol}
No need for @dfn in the index entries.
> +a CVS snapshot will have depricated @sc{mi} protocols, stable @sc{mi}
^^^^^^^^^^
"deprecated"
> +protocols and development @sc{mi} protocols. The depricated @sc{mi} protocols
^^^^^^^^^^
Same here.
> +eventually get removed. The @dfn{stable MI protocols} are considered stable
@dfn should be used only once, the first time you introduce the term.
After that, simply use the term without any markup or quoting.
next prev parent reply other threads:[~2004-11-06 10:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 19:57 Bob Rossi
2004-11-04 19:59 ` Bob Rossi
2004-11-11 20:30 ` Andrew Cagney
2004-11-12 3:44 ` Alain Magloire
2004-11-04 21:28 ` Eli Zaretskii
2004-11-05 16:39 ` Bob Rossi
2004-11-05 17:50 ` Eli Zaretskii
2004-11-05 22:12 ` Bob Rossi
2004-11-06 10:12 ` Eli Zaretskii [this message]
2004-11-08 14:49 ` Bob Rossi
2004-11-08 15:01 ` Eli Zaretskii
2004-11-12 9:54 Nick Roberts
[not found] <200411120344.WAA24018@smtp.ott.qnx.com>
2004-11-12 22:59 ` Andrew Cagney
2004-11-13 9:01 ` Eli Zaretskii
2004-11-13 13:48 ` Bob Rossi
2004-11-17 16:05 ` Alain Magloire
2004-11-17 16:32 ` Bob Rossi
2004-11-18 1:35 ` Alain Magloire
[not found] ` <200411180135.UAA14730@smtp.ott.qnx.com>
2004-11-19 19:23 ` Bob Rossi
2005-01-05 1:36 ` Bob Rossi
2005-01-05 1:51 ` Jim Ingham
2005-01-05 1:53 ` Bob Rossi
2005-01-05 2:01 ` Jim Ingham
2005-01-05 2:34 ` Bob Rossi
2005-01-05 2:40 ` Bob Rossi
2004-11-17 16:05 ` Alain Magloire
[not found] <200411171514.KAA17361@smtp.ott.qnx.com>
2004-11-17 17:30 ` 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='01c4c3e8$Blat.v2.2.2$853fdac0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--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