From: Doug Evans <dje@google.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [RFA] Add -s option to source command.
Date: Fri, 09 Apr 2010 00:13:00 -0000 [thread overview]
Message-ID: <l2ie394668d1004081713k273a8971y4351d6e3e2abf165@mail.gmail.com> (raw)
In-Reply-To: <201004082008.55981.sergiodj@redhat.com>
On Thu, Apr 8, 2010 at 4:08 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Thursday 08 April 2010 19:49:41, Doug Evans wrote:
>> On Wed, Apr 7, 2010 at 1:14 PM, Tom Tromey <tromey@redhat.com> wrote:
>> > I often wish that gdb help strings were formatted more like --help
>> > output.
>> >
>> > Tom
>>
>> Something like this?
>>
>> @@ -1379,8 +1437,12 @@ Commands defined in this way may have up
>>
>> source_help_text = xstrprintf (_("\
>> Read commands from a file named FILE.\n\
>> -Optional -v switch (before the filename) causes each command in\n\
>> -FILE to be echoed as it is executed.\n\
>> +\n\
>> +Usage: source [-s] [-v] FILE\n\
>> +-s: search for the script in the source search path,\n\
>> + even if FILE contains directories.\n\
>> +-v: each command in FILE is echoed as it is executed.\n\
>> +\n\
>> Note that the file \"%s\" is read automatically in this way\n\
>> when GDB is started."), gdbinit);
>> c = add_cmd ("source", class_support, source_command,
>
> I totally agree with Tom here, but I don't know if it's a good thing to change
> the "standard" only in this feature without converting the other GDB help
> strings as well. IMHO if we are going to start formatting the help strings
> like `--help' output, then we should do it for the majority (if not all) of
> the strings.
>
> Anyway, my half cent here.
Sure.
That one might want to wait and do it en-masse I left as a given.
The powers that be can decide, and I'll submit what they want.
next prev parent reply other threads:[~2010-04-09 0:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 21:58 Doug Evans
2010-04-06 23:17 ` Doug Evans
2010-04-07 20:14 ` Tom Tromey
2010-04-08 22:49 ` Doug Evans
2010-04-08 23:09 ` Sergio Durigan Junior
2010-04-09 0:13 ` Doug Evans [this message]
2010-04-09 17:15 ` Tom Tromey
2010-04-09 17:48 ` Eli Zaretskii
2010-04-10 1:29 ` Joel Brobecker
2010-04-09 7:49 ` Eli Zaretskii
2010-04-09 17:23 ` Doug Evans
2010-04-09 17:46 ` Eli Zaretskii
2010-04-09 18:12 ` Doug Evans
2010-04-09 19:31 ` Eli Zaretskii
2010-04-09 19:49 ` Doug Evans
2010-04-12 17:31 ` Doug Evans
2010-04-12 17:33 ` Doug Evans
2010-04-12 17:47 ` Tom Tromey
2010-04-12 17:54 ` Eli Zaretskii
2010-04-14 22:01 ` Doug Evans
2010-04-15 3:10 ` Eli Zaretskii
2010-04-09 17:13 ` Tom Tromey
2010-04-09 17:15 ` Doug Evans
2010-04-09 17:19 ` Tom Tromey
2010-04-17 15:20 ` H.J. Lu
2010-04-20 5:38 ` Doug Evans
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=l2ie394668d1004081713k273a8971y4351d6e3e2abf165@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tromey@redhat.com \
/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