Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 24/24] NEWS and manual changes for command options changes
Date: Thu, 23 May 2019 15:01:00 -0000	[thread overview]
Message-ID: <85dfe262-650b-af70-45f3-859445a419bb@redhat.com> (raw)
In-Reply-To: <83ftp57pw4.fsf@gnu.org>

On 5/23/19 5:31 AM, Eli Zaretskii wrote:>> From: Pedro Alves <palves@redhat.com>
>> Date: Wed, 22 May 2019 21:53:27 +0100
>>
>> gdb/ChangeLog:
>> yyyy-mm-dd  Pedro Alves  <palves@redhat.com>
>>
>> 	* NEWS (New commands): Mention "maint test-options
>> 	require-delimiter", "maint test-options unknown-is-error", "maint
>> 	test-options unknown-is-operand" and "maint show
>> 	test-options-completion-result".
>> 	(New command options, command completion): New section.
>> 	(Completion improvements): New section.
>> 	Mention that you can abbreviate "unlimited".
>>
>> gdb/doc/ChangeLog:
>> yyyy-mm-dd  Pedro Alves  <palves@redhat.com>
>>
>> 	* gdb.texinfo (Command Completion): Mention command options too.
>> 	(Command Options): New node.
>> 	(Threads): Add anchors.  Extend descriptions of the "taas" and
>> 	"tfaas" commands.
>> 	(Backtrace): Describe new options of the "backtrace" command.  Add
>> 	anchors.
>> 	(Frame Apply): Describe new options of the "frame apply" and
>> 	"faas" commands.  Add anchors.
>> 	(Data): Describe new options of the "print" command.  Add anchors.
>> 	(Compiling and Injecting Code): Mention options of the "compile
>> 	print" command.
>> 	(Maintenance Commands): Mention "maint test-options" subcommands
>> 	and the "maint show test-options-completion-result" command.
> 
> Thanks.  

Thank you.


>  A couple of minor comments.
> 
>> +apply all} command.  See @ref{thread apply all}.
> 
> I'd prefer @xref to "See @ref" at the beginning of a sentence.
> 
>> +apply} command.  See @ref{frame apply}.
> 
> Same here.
> 
>> +@item -past-main [@code{on}|@code{off}]
>> +Set whether backtraces should continue past "main".  Related setting:
> 
> "main" is a symbol, so please use @code{main}.
> 
>> +@item -entry-values @code{no}|@code{only}|@code{preferred}|@code{if-needed}|@code{both}|@code{compact}|@code{default}
> 
> Does this long line look reasonable in print?  If not, perhaps using
> just one meta-argument, followed by a table of possible values, would
> be better?

Looks good to me in pdf form.  It all fits in a single line.

> 
>> +@item -past-main [@code{on}|@code{off}]
>> +Whether backtraces should continue past "main".
> 
> Same issue with "main".
> 
>> +apply} command.  See @ref{frame apply}.
> 
> "See @ref" again.
> 
>> +@item -object [@code{on}|@code{off}]
>> +Set printing C++ virtual function tables.  Related setting: @ref{set
>                 ^^^
> C@t{++}, please (here and elsewhere in the patch).
> 
>> +@item -repeats @var{number-of-repeats}|@code{unlimited}
>> +Set threshold for repeated print elements. "unlimited" causes all
>                                             ^^
> Two spaces between sentences.  Also, "unlimited" at the sentence
> beginning looks awkward without capitalization.
> 

Hmm, "unlimited" is a literal, so I think we should use @code for it.
Is is OK this way?  I can rephrase a little to avoid @{unlimited} at
the beginning of the sentence, but I'm trying to be concise here,
since this is meant to be a brief outlook into the options, with a
reference to the "set" command anchor for more info.

Here are the changes I'm making to address your review:

---
 gdb/doc/gdb.texinfo | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index a7f92d1195d..ff06e7ceaa7 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -3293,7 +3293,7 @@ Shortcut for @code{thread apply all -s [@var{option}]@dots{} @var{command}}.
 Applies @var{command} on all threads, ignoring errors and empty output.
 
 The @code{taas} command accepts the same options as the @code{thread
-apply all} command.  See @ref{thread apply all}.
+apply all} command.  @xref{thread apply all}.
 
 @kindex tfaas
 @cindex apply a command to all frames of all threads (ignoring errors and empty output)
@@ -3315,7 +3315,7 @@ is, using:
 @end smallexample
 
 The @code{tfaas} command accepts the same options as the @code{frame
-apply} command.  See @ref{frame apply}.
+apply} command.  @xref{frame apply}.
 
 @kindex thread name
 @cindex name a thread
@@ -7593,7 +7593,7 @@ backtrace} and @code{set print} subcommands:
 
 @table @code
 @item -past-main [@code{on}|@code{off}]
-Set whether backtraces should continue past "main".  Related setting:
+Set whether backtraces should continue past @code{main}.  Related setting:
 @ref{set backtrace past-main}.
 
 @item -past-entry [@code{on}|@code{off}]
@@ -8087,7 +8087,7 @@ allow overriding relevant @code{set backtrace} settings:
 
 @table @code
 @item -past-main [@code{on}|@code{off}]
-Whether backtraces should continue past "main".
+Whether backtraces should continue past @code{main}.
 Related setting: @ref{set backtrace past-main}.
 
 @item -past-entry [@code{on}|@code{off}]
@@ -8179,7 +8179,7 @@ is, using:
 @end smallexample
 
 The @code{faas} command accepts the same options as the @code{frame
-apply} command.  See @ref{frame apply}.
+apply} command.  @xref{frame apply}.
 
 Note that the command @code{tfaas @var{command}} applies @var{command}
 on all frames of all threads.  See @xref{Threads,,Threads}.
@@ -9320,9 +9320,9 @@ Set printing of array indexes.
 Related setting: @ref{set print array-indexes}.
 
 @item -elements @var{number-of-elements}|@code{unlimited}
-Set limit on string chars or array elements to print.  "unlimited"
-causes there to be no limit.  Related setting: @ref{set print
-elements}.
+Set limit on string chars or array elements to print.
+@code{unlimited} causes there to be no limit.  Related setting:
+@ref{set print elements}.
 
 @item -max-depth @var{depth}|@code{unlimited}
 Set the threshold after which nested structures are replaced with
@@ -9333,20 +9333,20 @@ Set printing of char arrays to stop at first null char.  Related
 setting: @ref{set print null-stop}.
 
 @item -object [@code{on}|@code{off}]
-Set printing C++ virtual function tables.  Related setting: @ref{set
-print object}.
+Set printing C@t{++} virtual function tables.  Related setting:
+@ref{set print object}.
 
 @item -pretty [@code{on}|@code{off}]
 Set pretty formatting of structures.  Related setting: @ref{set print
 pretty}.
 
 @item -repeats @var{number-of-repeats}|@code{unlimited}
-Set threshold for repeated print elements. "unlimited" causes all
-elements to be individually printed.  Related setting: @ref{set print
-repeats}.
+Set threshold for repeated print elements.  @code{unlimited} causes
+all elements to be individually printed.  Related setting: @ref{set
+print repeats}.
 
 @item -static-members [@code{on}|@code{off}]
-Set printing C++ static members.  Related setting: @ref{set print
+Set printing C@t{++} static members.  Related setting: @ref{set print
 static-members}.
 
 @item -symbol [@code{on}|@code{off}]
-- 
2.14.5


  reply	other threads:[~2019-05-23 15:01 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 20:53 [PATCH 00/24] gdb::option framework, "print -OPT", other cmd options Pedro Alves
2019-05-22 20:53 ` [PATCH 19/24] Introduce complete_command Pedro Alves
2019-05-22 20:53 ` [PATCH 15/24] Introduce rename_cmd Pedro Alves
2019-05-25 19:58   ` Philippe Waroquiers
2019-05-29 16:03     ` Pedro Alves
2019-05-29 18:30       ` Pedro Alves
2019-05-30 10:22         ` Philippe Waroquiers
2019-05-30 20:01           ` Pedro Alves
2019-05-22 20:53 ` [PATCH 08/24] gdb.base/settings.exp: Fix comment typo Pedro Alves
2019-05-24 11:40   ` Pedro Alves
2019-05-22 20:53 ` [PATCH 07/24] Remove "show" command completers Pedro Alves
2019-05-23 19:28   ` Sergio Durigan Junior
2019-05-24 11:25     ` Pedro Alves
2019-05-24 14:21       ` Sergio Durigan Junior
2019-05-22 20:53 ` [PATCH 03/24] Fix TID parser bug Pedro Alves
2019-05-22 20:53 ` [PATCH 04/24] Make check_for_argument skip whitespace after arg itself Pedro Alves
2019-05-22 20:53 ` [PATCH 11/24] number_or_range_parser::get_number, don't treat "1 -" as a range Pedro Alves
2019-05-22 20:53 ` [PATCH 18/24] lib/completion-support.exp: Add test_gdb_completion_offers_commands Pedro Alves
2019-05-22 20:54 ` [PATCH 09/24] New set/show testing framework (gdb.base/settings.exp) Pedro Alves
2019-05-23  4:15   ` Eli Zaretskii
2019-05-22 20:54 ` [PATCH 21/24] "thread apply 1 -- -" vs "frame apply level 0 -- -" Pedro Alves
2019-05-22 20:54 ` [PATCH 12/24] Introduce generic command options framework Pedro Alves
2019-05-25  7:43   ` Philippe Waroquiers
2019-05-25 10:31     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 06/24] Fix "set enum-command value garbage" Pedro Alves
2019-05-23 19:13   ` Sergio Durigan Junior
2019-05-24 11:39     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 05/24] Allow "unlimited" abbreviations Pedro Alves
2019-05-22 20:54 ` [PATCH 01/24] Fix latent bug in custom word point completion handling Pedro Alves
2019-05-22 20:54 ` [PATCH 20/24] Make "frame apply" support -OPT options Pedro Alves
2019-05-25 20:12   ` Philippe Waroquiers
2019-05-29 15:13     ` Pedro Alves
2019-05-29 15:25       ` Pedro Alves
2019-05-22 20:54 ` [PATCH 14/24] Migrate rest of compile commands to new options framework Pedro Alves
2019-05-22 20:54 ` [PATCH 10/24] boolean/auto-boolean commands, make "o" ambiguous Pedro Alves
2019-05-22 20:54 ` [PATCH 22/24] Make "thread apply" use the gdb::option framework Pedro Alves
2019-05-25 20:24   ` Philippe Waroquiers
2019-05-29 15:38     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 02/24] Fix latent bug with custom word point completers Pedro Alves
2019-05-22 20:58 ` [PATCH 16/24] Make "backtrace" support -OPT options Pedro Alves
2019-05-22 20:58 ` [PATCH 13/24] Make "print" and "compile print" " Pedro Alves
2019-05-24 19:49   ` Sergio Durigan Junior
2019-05-25 10:10     ` Pedro Alves
2019-05-25 10:37       ` Andreas Schwab
2019-05-22 21:00 ` [PATCH 24/24] NEWS and manual changes for command options changes Pedro Alves
2019-05-23  4:31   ` Eli Zaretskii
2019-05-23 15:01     ` Pedro Alves [this message]
2019-05-23 15:07       ` Eli Zaretskii
2019-05-23 15:31         ` Pedro Alves
2019-05-25 20:40   ` Philippe Waroquiers
2019-05-29 16:03     ` Pedro Alves
2019-05-22 21:00 ` [PATCH 17/24] "backtrace full/no-filters/hide" completer Pedro Alves
2019-05-22 21:03 ` [PATCH 23/24] Delete parse_flags/parse_flags_qcs Pedro Alves
2019-05-22 21:46 ` [PATCH 00/24] gdb::option framework, "print -OPT", other cmd options Pedro Alves
2019-05-24 19:58 ` Sergio Durigan Junior

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=85dfe262-650b-af70-45f3-859445a419bb@redhat.com \
    --to=palves@redhat.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