Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: improve usage strings
Date: Sat, 11 Aug 2012 17:52:00 -0000	[thread overview]
Message-ID: <83ehndco4n.fsf@gnu.org> (raw)
In-Reply-To: <201208111336.41052.vapier@gentoo.org>

> From: Mike Frysinger <vapier@gentoo.org>
> Date: Sat, 11 Aug 2012 13:36:40 -0400
> Cc: gdb-patches@sourceware.org
> 
> static void
> finish_command (char *arg, int from_tty) 
> {
>   ...
> 
>   /* Find out whether we must run in the background.  */
>   if (arg != NULL)
>     async_exec = strip_bg_char (&arg);
> 
>   /* If we must run in the background, but the target can't do it,
>      error out.  */
>   if (async_exec && !target_can_async_p ())
>     error (_("Asynchronous execution not supported on this target."));
> 
>   /* If we are not asked to run in the bg, then prepare to run in the
>      foreground, synchronously.  */
>   if (!async_exec && target_can_async_p ())
>     {
>       /* Simulate synchronous execution.  */
>       async_disable_stdin ();
>     }
> 
>   if (arg)
>     error (_("The \"finish\" command does not take any arguments."));
>  ...
> 
> so it seems like finish *does* secretly accept options, but in this case it's 
> trying to be secret about it rather than someone just didn't fully document 
> it.  or i read the "arg" parsing logic above incorrectly.

Isn't that the case of "finish &" ?


  reply	other threads:[~2012-08-11 17:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11 16:55 Mike Frysinger
2012-08-11 17:16 ` Eli Zaretskii
2012-08-11 17:36   ` Mike Frysinger
2012-08-11 17:52     ` Eli Zaretskii [this message]
2012-08-11 18:08       ` Mike Frysinger
2012-08-14 15:08         ` Tom Tromey
2012-08-12  5:06     ` Doug Evans
2012-08-12  5:10       ` Mike Frysinger
2012-08-12 17:35       ` Eli Zaretskii
2012-08-13  2:06 ` [PATCH v2] " Mike Frysinger
2012-08-13 20:29   ` Doug Evans
2012-08-14  5:13     ` Mike Frysinger
2012-08-23 11:11     ` Pedro Alves
2012-08-14  5:29 ` [PATCH v3] " Mike Frysinger
2012-08-14 17:34   ` Doug Evans
2012-08-14 18:10     ` Eli Zaretskii
2012-08-15  1:58       ` Mike Frysinger
2012-08-15  7:22         ` Regression for gdb.base/help.exp [Re: [PATCH v3] gdb: improve usage strings] Jan Kratochvil
2012-08-15 16:25           ` Mike Frysinger
2012-08-15 16:27             ` Doug Evans
2012-08-20  4:29             ` Sergio Durigan Junior
2012-08-17  3:06           ` Mike Frysinger
2012-08-23 16:26         ` further improve "handle" help string Pedro Alves
2012-08-23 16:44           ` Eli Zaretskii
2012-08-23 17:18           ` Mike Frysinger
2012-08-23 17:38             ` Pedro Alves
2012-08-23 11:11     ` [PATCH v3] gdb: improve usage strings Pedro Alves
2012-08-23 16:45       ` 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=83ehndco4n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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