From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Adjust -list-features doc formatting
Date: Tue, 19 Aug 2008 13:14:00 -0000 [thread overview]
Message-ID: <200808191714.07332.vladimir@codesourcery.com> (raw)
Eli,
when reviewing my prior -list-target-features patch, you've suggested using
a @table thing for presenting a list of features. I've noticed that for
the -list-features command, introduced some time ago, docs uses @itemize --
presumably we need to adjust that one too. How about the attached patch?
- Volodya
[doc/ChangeLog]
* gdb.textinfo (GDB/MI Miscellaneous Commands): Use @table
for possible features of -list-features.
---
gdb/doc/gdb.texinfo | 21 ++++++++++-----------
1 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 100d795..61e9020 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -22624,18 +22624,17 @@ Example output:
The current list of features is:
-@itemize @minus
-@item
-@samp{frozen-varobjs}---indicates presence of the
-@code{-var-set-frozen} command, as well as possible presense of the
-@code{frozen} field in the output of @code{-varobj-create}.
-@item
-@samp{pending-breakpoints}---indicates presence of the @code{-f}
-option to the @code{-break-insert} command.
-@item
-@samp{thread-info}---indicates presence of the @code{-thread-info} command.
+@table @samp
+@item frozen-varobjs
+Indicates presence of the @code{-var-set-frozen} command, as well
+as possible presense of the @code{frozen} field in the output
+of @code{-varobj-create}.
+@item pending-breakpoints
+Indicates presence of the @code{-f} option to the @code{-break-insert} command.
+@item thread-info
+Indicates presence of the @code{-thread-info} command.
-@end itemize
+@end table
@subheading The @code{-list-target-features} Command
@findex -list-target-features
--
1.5.3.5
next reply other threads:[~2008-08-19 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 13:14 Vladimir Prus [this message]
2008-08-19 18:52 ` 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=200808191714.07332.vladimir@codesourcery.com \
--to=vladimir@codesourcery.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