From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, dje@google.com, gdb@sourceware.org
Subject: Re: improved thread id reporting
Date: Sun, 05 Apr 2009 18:23:00 -0000 [thread overview]
Message-ID: <83ws9zaro2.fsf@gnu.org> (raw)
In-Reply-To: <200904050719.n357JYXJ013198@brahms.sibelius.xs4all.nl>
> Date: Sun, 5 Apr 2009 09:19:34 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: dje@google.com, gdb@sourceware.org
>
> > Date: Sat, 4 Apr 2009 21:11:34 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > On Sat, Apr 04, 2009 at 03:17:02PM -0700, Doug Evans wrote:
> > > > That said, if it's possible to print them without creating additional
> > > > line breaks on an 80-column wide screen, I have no objections.
> > > >
> > > >> To fix (1) I'd like to simply remove the pthread id from the output.
> > > >
> > > > I think that's a bad idea.
> > >
> > > Even as a user-settable option?
> >
> > IMO, yes. I don't think we need more settable options for details of
> > output formatting; 98% or so of users will use the default, so that's
> > the part that matters.
>
> Seconded.
Then we appear to have a draw, because I happen to agree with Doug.
And I really don't understand the argument against a user option: it
wasn't suggested as a means to get what, according to Daniel and Mark,
the majority of users need; it was suggested as a means for Doug (and
other minorities) to get what they want. An option that is used in
rare situations by people with unconventional requests can hardly do
any real harm, because if Daniel and Mark are right, no one except
Doug will ever miss it or even know it exists.
next prev parent reply other threads:[~2009-04-05 18:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 19:06 Doug Evans
2009-04-04 19:07 ` Mark Kettenis
2009-04-04 20:40 ` Daniel Jacobowitz
2009-04-04 21:21 ` Eli Zaretskii
2009-04-04 22:17 ` Daniel Jacobowitz
2009-04-05 1:11 ` Doug Evans
2009-04-05 3:42 ` Eli Zaretskii
2009-04-05 3:48 ` Daniel Jacobowitz
2009-04-05 7:19 ` Paul Pluzhnikov
2009-04-05 18:50 ` Eli Zaretskii
2009-04-05 20:11 ` Paul Pluzhnikov
2009-04-05 20:36 ` Eli Zaretskii
2009-04-04 22:35 ` Doug Evans
2009-04-06 2:58 ` Doug Evans
2009-04-06 3:33 ` Eli Zaretskii
2009-04-06 15:36 ` Mark Kettenis
2009-04-06 20:21 ` Eli Zaretskii
2009-04-06 7:39 ` Daniel Jacobowitz
2009-04-06 21:21 ` Eli Zaretskii
2009-05-08 5:43 ` Doug Evans
2009-04-06 20:20 ` Tom Tromey
2009-04-06 20:20 ` Eli Zaretskii
2009-04-06 22:15 ` Tom Tromey
2009-04-07 15:18 ` Doug Evans
2009-04-04 22:24 ` Doug Evans
2009-04-05 3:13 ` Daniel Jacobowitz
2009-04-05 9:16 ` Mark Kettenis
2009-04-05 18:23 ` Eli Zaretskii [this message]
2009-04-05 19:22 ` Doug Evans
2009-04-04 19:20 ` Thiago Jung Bauermann
2009-04-04 19:21 ` Eli Zaretskii
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=83ws9zaro2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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