public inbox for gdb-patches@sourceware.org
 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 2/2] Star wildcard ranges (e.g., "info thread 2.*")
Date: Thu, 14 Jan 2016 11:13:00 -0000	[thread overview]
Message-ID: <569782EB.2030509@redhat.com> (raw)
In-Reply-To: <83k2ndifd4.fsf@gnu.org>

On 01/13/2016 05:00 PM, Eli Zaretskii wrote:
>> From: Pedro Alves <palves@redhat.com>
>> Date: Wed, 13 Jan 2016 16:34:45 +0000
>>
>> Add support for specifying "all threads of inferior N", by writing "*"
>> as thread number/range in thread ID lists.
>>
>> E.g., "info threads 2.*" or "thread apply 2.* bt".
> 
> Thanks.
> 
>> +* In commands that accept thread IDs lists, you can now refer to all
> 
> "thread ID lists", only one word in plural.  Or maybe even better:
> "lists of thread IDs".

Hmm, going further, I think that "list" should be singular too:

 In commands that accept a thread ID list, you can now refer to all
 In commands that accept a list of thread IDs, you can now refer to all

I prefer the former because "thread ID list" is a defined term in
the manual.

> 
>> +argument.  A list element can be:
>> +
>> +@enumerate
>> +@item
>> +a thread ID as shown in the first field of the @samp{info threads}
>> +display, with or without an inferior qualifier.  E.g., @samp{2.1} or
>> +@samp{1}.
>> +
>> +@item
>> +a range of thread numbers, again with or without an inferior
>> +qualifier, as in @var{inf}.@var{thr1}-@var{thr2} or
>> +@var{thr1}-@var{thr2}.  E.g., @samp{1.2-4} or @samp{2-4}.
>> +
>> +@item
>> +all threads of an inferior, specified with a star wildcard, with or
>> +without an inferior qualifier, as in @var{inf}.@code{*} (e.g.,
>> +@samp{1.*}) or @code{*}.  The former refers to all threads of the
>> +given inferior, and the latter form without an inferior qualifier
>> +refers to all threads of the current inferior.
> 
> In this enumeration, each item begins with a lower-case letter, and
> then continues with another sentence.  I suggest to capitalize the
> first letter of each item, to be more grammatically correct.
> 
> Otherwise, the documentation parts are OK.

Thanks.  Here's the diff that I'm squashing in with the original version.

diff --git a/gdb/NEWS b/gdb/NEWS
index c00dac9..be3536c 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -34,7 +34,7 @@
      [Switching to thread 2.1 (Thread 0x7ffff7fc2740 (LWP 8157))] (running)
      (gdb)

-* In commands that accept thread IDs lists, you can now refer to all
+* In commands that accept a thread ID list, you can now refer to all
   threads of an inferior using a star wildcard.  GDB accepts
   "INF_NUM.*", to refer to all threads of inferior INF_NUM, and "*" to
   refer to all threads of the current inferior.  For example, "info

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index fbc76fa..a08a196 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -2916,17 +2916,17 @@ argument.  A list element can be:

 @enumerate
 @item
-a thread ID as shown in the first field of the @samp{info threads}
+A thread ID as shown in the first field of the @samp{info threads}
 display, with or without an inferior qualifier.  E.g., @samp{2.1} or
 @samp{1}.

 @item
-a range of thread numbers, again with or without an inferior
+A range of thread numbers, again with or without an inferior
 qualifier, as in @var{inf}.@var{thr1}-@var{thr2} or
 @var{thr1}-@var{thr2}.  E.g., @samp{1.2-4} or @samp{2-4}.

 @item
-all threads of an inferior, specified with a star wildcard, with or
+All threads of an inferior, specified with a star wildcard, with or
 without an inferior qualifier, as in @var{inf}.@code{*} (e.g.,
 @samp{1.*}) or @code{*}.  The former refers to all threads of the
 given inferior, and the latter form without an inferior qualifier
-- 
1.9.3


  reply	other threads:[~2016-01-14 11:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 16:34 [PATCH 0/2] " Pedro Alves
2016-01-13 16:34 ` [PATCH 2/2] " Pedro Alves
2016-01-13 17:00   ` Eli Zaretskii
2016-01-14 11:13     ` Pedro Alves [this message]
2016-01-14 16:16       ` Eli Zaretskii
2016-01-14 16:42         ` Pedro Alves
2016-01-14 11:29   ` Pedro Alves
2016-01-13 16:34 ` [PATCH 0/2] " Pedro Alves
2016-01-13 16:42   ` Pedro Alves
2016-01-13 16:34 ` [PATCH 1/2] Fix "thread apply $conv_var" and misc other related problems Pedro Alves
2016-01-14 16:52 ` [PATCH 0/2] Star wildcard ranges (e.g., "info thread 2.*") Simon Marchi
2016-01-15 21:50 ` Pedro Alves
2016-01-14 11:39 Pedro Alves
2016-01-14 11:39 ` [PATCH 2/2] " Pedro Alves

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=569782EB.2030509@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).