From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit+doco] GDB/MI: Document support for -exec-run --start in -list-features
Date: Mon, 23 Dec 2013 04:28:00 -0000 [thread overview]
Message-ID: <20131223042841.GF4605@adacore.com> (raw)
In-Reply-To: <83bo088bxh.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
> > gdb/doc/ChangeLog:
> >
> > * gdb.texinfo (GDB/MI Support Commands): Add @findex entries
> > for each @item in the table describing the list of features.
> > Add empty line between each @item.
> >
> > OK to commit?
>
> It is OK, but the same effect for a much smaller effort would be
> achieved by replacing @table with @ftable. Thgen each @item
> automatically gets inserted into the function index.
I didn't know that, thanks! Here is a new patch...
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Support Commands): Change @table into
@ftable.
--
Joel
[-- Attachment #2: 0001-Turn-list-feature-table-into-ftable.patch --]
[-- Type: text/x-diff, Size: 1268 bytes --]
From 86e54f9d0fa850ad464be97defd082a0224bd61b Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Mon, 23 Dec 2013 05:33:59 +0400
Subject: [PATCH] Turn -list-feature @table into @ftable.
This is to make it easier to discover the various options displayed
by the -list-features command.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Support Commands): Change @table into
@ftable.
---
gdb/doc/gdb.texinfo | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 29f1cfc..8814cd0 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -35114,7 +35114,7 @@ Example output:
The current list of features is:
-@table @samp
+@ftable @samp
@item frozen-varobjs
Indicates support for the @code{-var-set-frozen} command, as well
as possible presense of the @code{frozen} field in the output
@@ -35148,7 +35148,7 @@ records, produced when trying to execute an undefined @sc{gdb/mi} command
@item exec-run-start-option
Indicates that the @code{-exec-run} command supports the @option{--start}
option (@pxref{GDB/MI Program Execution}).
-@end table
+@end ftable
@subheading The @code{-list-target-features} Command
@findex -list-target-features
--
1.8.3.2
next prev parent reply other threads:[~2013-12-23 4:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 6:21 Joel Brobecker
2013-12-03 7:22 ` Eli Zaretskii
2013-12-03 10:18 ` Joel Brobecker
2013-12-10 12:03 ` Joel Brobecker
2013-12-10 17:39 ` Eli Zaretskii
2013-12-12 16:02 ` pushed: Add @cindex for section documenting the -list-features GDB/MI command. (was: "[RFA/commit+doco] GDB/MI: Document support for -exec-run --start in -list-features") Joel Brobecker
2013-12-12 16:35 ` Eli Zaretskii
2013-12-13 6:10 ` [RFA/commit+doco] GDB/MI: Document support for -exec-run --start in -list-features Joel Brobecker
2013-12-13 15:51 ` Joel Brobecker
2013-12-13 19:36 ` Eli Zaretskii
2013-12-23 1:01 ` Joel Brobecker
2013-12-23 1:40 ` Joel Brobecker
2013-12-23 3:49 ` Eli Zaretskii
2013-12-23 4:28 ` Joel Brobecker [this message]
2013-12-23 16:10 ` Eli Zaretskii
2013-12-28 3:10 ` pushed: " Joel Brobecker
2013-12-10 11:14 ` Joel Brobecker
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=20131223042841.GF4605@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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