Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Spencer Baugh <sbaugh@catern.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add "-a" option for inferior commands
Date: Wed, 22 Feb 2017 21:11:00 -0000	[thread overview]
Message-ID: <95f9622e067422a442bb97e85dd27c65@polymtl.ca> (raw)
In-Reply-To: <87mvde6im3.fsf@catern.com>

On 2017-02-22 16:06, Spencer Baugh wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>> On Feb 21 2017, Spencer Baugh <sbaugh@catern.com> wrote:
>> 
>>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>>> On Dez 29 2016, Spencer Baugh <sbaugh@catern.com> wrote:
>>>> 
>>>>> @@ -1055,8 +1101,8 @@ as main program."));
>>>>>    set_cmd_completer (c, filename_completer);
>>>>> 
>>>>>    add_com ("remove-inferiors", no_class, remove_inferior_command, 
>>>>> _("\
>>>>> -Remove inferior ID (or list of IDs).\n\
>>>>> -Usage: remove-inferiors ID..."));
>>>>> +Remove inferior ID (or list of IDs, or all inferiors with -a).\n\
>>>>> +Usage: remove-inferiors [-a] ID..."));
>>>> 
>>>> What is the meaning of ID if -a is present?
>>> 
>>> ID is ignored if -a is present.
>> 
>> Shouldn't ID be optional then?
> 
> Like this then?
> 
> Usage: remove-inferiors [-a] [ID...]
> 
> I was just concerned that that doesn't indicate that one of them must 
> be
> present. Not sure what the convention is to indicate that.

An option would be to have multiple lines.  Not sure how to format it, 
but something like:

   (gdb) help remove-inferiors
   Remove inferior ID (or list of IDS)
   Usage: remove-inferiors ID...

   Remove all inferiors
   Usage: remove-inferiors -a

It would be nice to decide on a standard format for help messages, kind 
of like man pages always have the same format.

Simon


      reply	other threads:[~2017-02-22 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 20:55 Spencer Baugh
2016-12-29 21:38 ` Andreas Schwab
2016-12-29 22:01   ` sbaugh
2017-02-22  4:28   ` Spencer Baugh
2017-02-22  9:24     ` Andreas Schwab
2017-02-22 21:06       ` Spencer Baugh
2017-02-22 21:11         ` Simon Marchi [this message]

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=95f9622e067422a442bb97e85dd27c65@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=sbaugh@catern.com \
    --cc=schwab@linux-m68k.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