From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch/doc] Tweak "info inferiors" output.
Date: Mon, 17 Aug 2009 17:55:00 -0000 [thread overview]
Message-ID: <83hbw6ibcl.fsf@gnu.org> (raw)
In-Reply-To: <200908171537.27573.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 17 Aug 2009 15:37:27 +0100
>
> Before
> I change that, if we were to add column headers to "info threads", what
> would we call it's second column? This is really the same thing
> applied to inferiors.
Let me turn the table around and ask you how about if we remove the
column headers from "info inferiors" display, like with "info
threads"?
> Here's what the docs say when describing "info threads":
>
> @item
> the target system's thread identifier (@var{systag})
> @end enumerate
I can live with that.
> > For processes, I'd prefer "process (PID NNN)".
>
> Hmm, not sure. The data in parentheses looks like
> something that isn't mandatory to be displayed, just
> something extra when there's row space for it. But, just "process"
> doesn't make sense here.
We use something similar to my suggestion when we report the LWP
thread IDs. But I see now that we use "process NNN" in "info
threads", so I guess there are precedents and we can go with your
original suggestion, although I can't say I like this form.
> What do you think of this one?
It's fine, thanks.
> We just need to settle on the column name, I think.
Or lack thereof ;-)
> +An asterisk @samp{*} to the left of the @value{GDBN} inferior number
That's really a nit, but if we ever get GDB speak other languages,
that ``to the left of'' will be incorrect with some languages. Maybe
``preceding the @value{GDBN} inferior number'' is better.
next prev parent reply other threads:[~2009-08-17 17:47 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 [this message]
2009-08-17 18:01 ` Tom Tromey
2009-08-17 19:28 ` Eli Zaretskii
2009-08-17 20:12 ` Stan Shebs
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=83hbw6ibcl.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