From: Tom Tromey <tromey@redhat.com>
To: Daniel Gutson <daniel.gutson@tallertechnologies.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: specifying gdb's exit code
Date: Wed, 23 Apr 2014 17:11:00 -0000 [thread overview]
Message-ID: <87ppk89dir.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAF5HaEX1jfUdDkH3FrNviGYezWog5oyVF3WYM6mwmP=EtrvCjQ@mail.gmail.com> (Daniel Gutson's message of "Thu, 17 Apr 2014 18:51:57 -0300")
>>>>> "Daniel" == Daniel Gutson <daniel.gutson@tallertechnologies.com> writes:
Daniel> What about this?
Daniel> (I'm not a native English speaker)
I wonder what you think of the appended.
It adds an explicit "Usage" line, which gdb does in a few other spots
and which I think it generally the most clear approach.
Tom
diff --git a/gdb/cli/cli-cmds.c b/gdb/cli/cli-cmds.c
index bfcd975..298f54c 100644
--- a/gdb/cli/cli-cmds.c
+++ b/gdb/cli/cli-cmds.c
@@ -1685,7 +1685,11 @@ strict == evaluate script according to filename extension, error if not supporte
show_script_ext_mode,
&setlist, &showlist);
- add_com ("quit", class_support, quit_command, _("Exit gdb."));
+ add_com ("quit", class_support, quit_command, _("\
+Exit gdb.\n\
+Usage: quit [CODE]\n\
+The optional argument CODE, if present, is used as gdb's exit status.\n\
+The default is zero."));
c = add_com ("help", class_support, help_command,
_("Print list of commands."));
set_cmd_completer (c, command_completer);
next prev parent reply other threads:[~2014-04-23 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF5HaEVTZAxc0FNR9GnGNKJqxGSrbQaTfZ7ZRMoueTg6jQyL8A@mail.gmail.com>
[not found] ` <CAF5HaEWDv6Gb2m-iDpzcM4y_ybkT46R1b96xxdS9buLHbsgwRQ@mail.gmail.com>
[not found] ` <CADPb22RS0J3X8hcBiUiDPp62RYiKPE4vCSPV5WEMUF01KzsiLg@mail.gmail.com>
[not found] ` <CAF5HaEV3wMHXfk3jLmbY-E6XAaZSmBRhzDjo2BvhQ7NbvvCtZQ@mail.gmail.com>
2014-04-17 21:52 ` Daniel Gutson
2014-04-22 12:37 ` Daniel Gutson
2014-04-23 17:11 ` Tom Tromey [this message]
2014-04-23 17:29 ` Pedro Alves
2014-04-23 17:36 ` Paul_Koning
2014-04-23 17:46 ` Pedro Alves
2014-04-23 17:49 ` Tom Tromey
2014-04-23 17:57 ` Pedro Alves
2014-04-25 15:44 ` Tom Tromey
2014-04-23 18:17 ` Paul_Koning
2014-04-23 18:23 ` Tom Tromey
2014-04-23 20:53 ` Daniel Gutson
2014-04-23 20:55 ` Daniel Gutson
2014-04-23 17:29 ` Eli Zaretskii
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=87ppk89dir.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=daniel.gutson@tallertechnologies.com \
--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