From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19891 invoked by alias); 17 Aug 2009 19:57:33 -0000 Received: (qmail 19876 invoked by uid 22791); 17 Aug 2009 19:57:32 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Aug 2009 19:57:26 +0000 Received: (qmail 9294 invoked from network); 17 Aug 2009 19:57:25 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 Aug 2009 19:57:25 -0000 Message-ID: <4A89B61F.5090307@codesourcery.com> Date: Mon, 17 Aug 2009 20:12:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Eli Zaretskii CC: tromey@redhat.com, pedro@codesourcery.com, gdb-patches@sourceware.org Subject: Re: [patch/doc] Tweak "info inferiors" output. References: <200908141646.01031.pedro@codesourcery.com> <200908142016.00060.pedro@codesourcery.com> <834osajgrf.fsf@gnu.org> <200908171537.27573.pedro@codesourcery.com> <83hbw6ibcl.fsf@gnu.org> <83eirai8et.fsf@gnu.org> In-Reply-To: <83eirai8et.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-08/txt/msg00261.txt.bz2 Eli Zaretskii wrote: >> From: Tom Tromey >> Cc: Pedro Alves , gdb-patches@sourceware.org >> Date: Mon, 17 Aug 2009 11:52:46 -0600 >> >> >>>>>>> "Eli" == Eli Zaretskii 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