From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Add the "-info-os" command to MI
Date: Fri, 08 Jun 2012 22:58:00 -0000 [thread overview]
Message-ID: <4FD28387.40005@earthlink.net> (raw)
In-Reply-To: <jqa4d2$8l5$1@dough.gmane.org>
On 6/1/12 3:09 AM, Vladimir Prus wrote:
> On 23/05/12 18:38, Stan Shebs wrote:
>> @{width="10",alignment="-1",col_name="col1",colhdr="Description"@}],
>> +body=[item=@{col0="processes",col1="Listing of all processes"@},
>> + item=@{col0="procgroups",col1="Listing of all process groups"@},
>> + item=@{col0="threads",col1="Listing of all threads"@},
>> + item=@{col0="files",col1="Listing of all file descriptors"@},
>> + item=@{col0="sockets",col1="Listing of all internet-domain
>> sockets"@},
>> + item=@{col0="shm",col1="Listing of all shared-memory regions"@},
>> + item=@{col0="semaphores",col1="Listing of all semaphores"@},
>> + item=@{col0="msg",col1="Listing of all message queues"@},
>> + item=@{col0="modules",col1="Listing of all loaded kernel
>
> Stan,
>
> I am afraid this output is not really good enough. From MI consumer
> standpoint, we need a clear
> and concise labels for each resource type. Unfortunately, "shm" is not
> acceptable at all.
> "Listing of all shared-memory regions" is unacceptably long. Besides,
> this would make a good title
> for a table with output, but not really good title for a menu used to
> specify what to show. For
> the record, here's the labels I have to use in actual UI code:
>
> ResourceClassContributionItem_0=Processes
> ResourceClassContributionItem_10=Shared memory regions
> ResourceClassContributionItem_12=Semaphores
> ResourceClassContributionItem_14=Message queues
> ResourceClassContributionItem_16=Kernel modules
> ResourceClassContributionItem_2=Process groups
> ResourceClassContributionItem_4=Threads
> ResourceClassContributionItem_6=Files
> ResourceClassContributionItem_8=Sockets
>
> Could GDB be made to output such labels?
Thinking about this a bit, it would work to add a third column to the
types listing, call it "Title", and define it as something like "short
distinctive phrase using whole words" or something like that, and with a
note in the manual that the title would ideally be phrased to be
suitable for a menu of types. This lets it occupy a middle ground
between the ultra-short string that is suitable for a subcommand in the
CLI, and the fully description that is suitable to head up a listing of
objects.
I'll work up a patch along these lines. In keeping with the apparent
tradition of numbered columns in the listing of types :-), I'll supply
titles as "col2".
Stan
next prev parent reply other threads:[~2012-06-08 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 0:29 Stan Shebs
2012-05-23 11:15 ` Pedro Alves
2012-05-23 14:39 ` Stan Shebs
2012-06-01 10:10 ` Vladimir Prus
2012-06-08 22:58 ` Stan Shebs [this message]
2012-06-12 1:13 ` Stan Shebs
2012-06-12 14:51 ` Tom Tromey
2012-06-25 12:28 ` Vladimir Prus
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=4FD28387.40005@earthlink.net \
--to=stanshebs@earthlink.net \
--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