From: Stan Shebs <stan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [patch/doc] Tweak "info inferiors" output.
Date: Mon, 17 Aug 2009 20:12:00 -0000 [thread overview]
Message-ID: <4A89B61F.5090307@codesourcery.com> (raw)
In-Reply-To: <83eirai8et.fsf@gnu.org>
Eli Zaretskii wrote:
>> From: Tom Tromey <tromey@redhat.com>
>> Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
>> Date: Mon, 17 Aug 2009 11:52:46 -0600
>>
>>
>>>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>>>>>>>
>> Eli> Let me turn the table around and ask you how about if we remove the
>> Eli> column headers from "info inferiors" display, like with "info
>> Eli> threads"?
>>
>> Please don't. The column headers provide actually useful information to
>> the user. It is a bug that info threads doesn't have them.
>>
>
> Fair enough, but then please suggest useful headers for these two
> displays.
>
I think "ID" for the first column is fine, and maybe just "Description"
for the second. I don't think we require targets to promise uniqueness
for their own info, and the column headers are just hints, not complete
documentation on what one might expect to see in the column; so it
should be something a little vague and generic.
We alway change it later if user feedback is negative.
Stan
next prev parent reply other threads:[~2009-08-17 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 16:22 Pedro Alves
2009-08-14 17:38 ` Tom Tromey
2009-08-14 18:30 ` Eli Zaretskii
2009-08-14 19:27 ` Pedro Alves
2009-08-14 20:59 ` Eli Zaretskii
2009-08-17 14:37 ` Pedro Alves
2009-08-17 14:45 ` Pedro Alves
2009-08-17 17:55 ` Eli Zaretskii
2009-08-17 18:01 ` Tom Tromey
2009-08-17 19:28 ` Eli Zaretskii
2009-08-17 20:12 ` Stan Shebs [this message]
2009-08-24 11:15 ` Pedro Alves
2009-08-24 18:54 ` Eli Zaretskii
2009-08-25 15:40 ` 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=4A89B61F.5090307@codesourcery.com \
--to=stan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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