From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fix PR gdb/8869
Date: Thu, 13 Aug 2009 17:34:00 -0000 [thread overview]
Message-ID: <83fxbvk548.fsf@gnu.org> (raw)
In-Reply-To: <200908131603.04422.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Thu, 13 Aug 2009 16:03:03 +0100
>
> (gdb) set language
> Requires an argument. Valid arguments are unknown, local, auto, ada, c, c++, asm, minimal, fortran, objective-c, java, modula-2, pascal, scheme.
>
> vs.
>
> (gdb) set language
> Requires an argument. Valid arguments are auto, local, unknown, ada, c, c++, asm, minimal, fortran, objective-c, java, modula-2, pascal, scheme.
>
> "Valid arguments are unknown" strikes me as odd.
You could say
Valid arguments are: unknown, local, auto, ...
It is also more grammatically correct, I believe.
> I guess we can also claim that it is weird that
> "set language" doesn't show an alphabetically sorted list, while
> "set language<TAB>" does. Anyone bothered enough to go address that?
I indeed think the list should be alphabetized. As the list grows,
having any other order will make it easier to miss some language you
are looking for.
next prev parent reply other threads:[~2009-08-13 17:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:48 Tom Tromey
2009-08-07 22:05 ` Tom Tromey
2009-08-07 22:16 ` Pedro Alves
2009-08-07 22:29 ` Tom Tromey
2009-08-08 1:55 ` Tom Tromey
2009-08-08 16:17 ` Pedro Alves
2009-08-08 16:39 ` Pedro Alves
2009-08-08 18:08 ` Pedro Alves
2009-08-12 23:00 ` Tom Tromey
2009-08-13 17:06 ` Pedro Alves
2009-08-13 17:34 ` Eli Zaretskii [this message]
2009-08-13 18:30 ` Pedro Alves
2009-08-08 8:37 ` Eli Zaretskii
2009-08-10 17:59 ` Tom Tromey
2009-08-10 19:38 ` Eli Zaretskii
2009-08-10 19:59 ` Tom Tromey
2009-08-10 20:10 ` 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=83fxbvk548.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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