From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Kwok Cheung Yeung <kcy@codesourcery.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Add the "-info-os" command to MI
Date: Tue, 06 Dec 2011 18:53:00 -0000 [thread overview]
Message-ID: <201112061845.33688.pedro@codesourcery.com> (raw)
In-Reply-To: <4ECD83B2.2070909@codesourcery.com>
On Wednesday 23 November 2011 23:37:22, Kwok Cheung Yeung wrote:
> >> +@smallexample
> >> +(gdb)
> >> +-info-os
> >> +^done,OSDataTable=@{nr_rows="9",nr_cols="2",hdr=[@{width="10",alignment=
> >> +"-1",col_name="col0",colhdr="Type"@},@{width="10",alignment="-1",col_nam
> >> +e="col1",colhdr="Description"@}],body=[item=@{col0="processes",col1="Lis
> >> +ting of all processes"@},item=@{col0="procgroups",col1="Listing of all p
> >> +rocess groups"@},item=@{col0="threads",col1="Listing of all threads"@},i
> >> +tem=@{col0="files",col1="Listing of all file descriptors"@},item=@{col0=
> >> +"sockets",col1="Listing of all internet-domain sockets"@},item=@{col0="s
> >> +hm",col1="Listing of all shared-memory regions"@},item=@{col0="semaphore
> >> +s",col1="Listing of all semaphores"@},item=@{col0="msg",col1="Listing of
> >> + all message queues"@},item=@{col0="modules",col1="Listing of all loaded
> >> + kernel modules"@}]@}
> >
> > The lines here are broken in arbitrary places, which will look
> > illegible in the manual. Please reformat the example so that the
> > output could be readable by humans.
> >
>
> Well, one could argue that MI wasn't meant to be easily human-readable :-) That
> output is exactly how it would look if the command were issued by a human, and
> it might be confusing if a user issues the command and doesn't get the nicely
> formatted output shown in the manual. I'm happy to make the changes if you think
> that is not an issue though.
Yes, that is not an issue. We have other examples of a putting breaks in place
to make it more readable. See e.g., the example of "-list-thread-groups".
--
Pedro Alves
next prev parent reply other threads:[~2011-12-06 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 15:52 Kwok Cheung Yeung
2011-10-13 16:13 ` Eli Zaretskii
2011-11-23 23:37 ` Kwok Cheung Yeung
2011-12-06 18:53 ` Pedro Alves [this message]
2011-10-21 20:53 ` Tom Tromey
2011-10-27 0:24 ` Stan Shebs
2011-10-27 16:45 ` Tom Tromey
2011-11-24 23:15 ` Kwok Cheung Yeung
2011-11-25 11:56 ` Eli Zaretskii
2011-11-29 19:01 ` Tom Tromey
2011-11-29 23:18 ` Kwok Cheung Yeung
2011-11-30 14:47 ` Tom Tromey
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=201112061845.33688.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kcy@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