Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 01:40:00 -0000	[thread overview]
Message-ID: <20131223014015.GE4605@adacore.com> (raw)
In-Reply-To: <20131210120252.GD3238@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

Next step in the patch series is to add @findex'es for each
item in the -list-features table. This one was purely mechanical...

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?

Thank you,
-- 
Joel

[-- Attachment #2: 0001-Add-findex-for-each-item-of-list-features.patch --]
[-- Type: text/x-diff, Size: 2936 bytes --]

From 48758b378554b9b148c86ff94c8d0f5a0bff054b Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Mon, 23 Dec 2013 05:33:59 +0400
Subject: [PATCH] Add @findex for each @item of -list-features

This is to make it easier to discover the various options displayed
by the -list-features command.

It also adds an empty line between each @item of the table, for
added clarity.  Otherwise, it is becoming harder to visually
separate each entry, and thus edit that part of the file.

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.
---
 gdb/doc/gdb.texinfo | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 29f1cfc..6b8241d 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -35115,39 +35115,62 @@ Example output:
 The current list of features is:
 
 @table @samp
+
 @item frozen-varobjs
+@findex frozen-varobjs
 Indicates support for 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
+@findex pending-breakpoints
 Indicates support for the @option{-f} option to the @code{-break-insert}
 command.
+
 @item python
+@findex python
 Indicates Python scripting support, Python-based
 pretty-printing commands, and possible presence of the
 @samp{display_hint} field in the output of @code{-var-list-children}
+
 @item thread-info
+@findex thread-info
 Indicates support for the @code{-thread-info} command.
+
 @item data-read-memory-bytes
+@findex data-read-memory-bytes
 Indicates support for the @code{-data-read-memory-bytes} and the
 @code{-data-write-memory-bytes} commands.
+
 @item breakpoint-notifications
+@findex breakpoint-notifications
 Indicates that changes to breakpoints and breakpoints created via the
 CLI will be announced via async records.
+
 @item ada-task-info
+@findex ada-task-info
 Indicates support for the @code{-ada-task-info} command.
+
 @item language-option
+@findex language-option
 Indicates that all @sc{gdb/mi} commands accept the @option{--language}
 option (@pxref{Context management}).
+
 @item info-gdb-mi-command
+@findex info-gdb-mi-command
 Indicates support for the @code{-info-gdb-mi-command} command.
+
 @item undefined-command-error-code
+@findex undefined-command-error-code
 Indicates support for the "undefined-command" error code in error result
 records, produced when trying to execute an undefined @sc{gdb/mi} command
 (@pxref{GDB/MI Result Records}).
+
 @item exec-run-start-option
+@findex exec-run-start-option
 Indicates that the @code{-exec-run} command supports the @option{--start}
 option (@pxref{GDB/MI Program Execution}).
+
 @end table
 
 @subheading The @code{-list-target-features} Command
-- 
1.8.3.2


  parent reply	other threads:[~2013-12-23  1:40 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 [this message]
2013-12-23  3:49       ` Eli Zaretskii
2013-12-23  4:28         ` Joel Brobecker
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=20131223014015.GE4605@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