From: Christoph Hellwig <hch@infradead.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 1/2] perf tools: Add --tui and --stdio to choose the UI
Date: Sat, 21 Aug 2010 13:47:54 -0400 [thread overview]
Message-ID: <20100821174754.GA10213@infradead.org> (raw)
In-Reply-To: <1282412712-3547-2-git-send-email-acme@infradead.org>
On Sat, Aug 21, 2010 at 02:45:11PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Relying just on ~/.perfconfig or rebuilding the tool disabling support
> for the TUI is too cumbersome, so allow specifying which UI to use and
> make the command line switch override whatever is in ~/.perfconfig.
Much better than the current situation, thanks!
I still thinks commands like perf report should not be overloaded for
two different user interfaces, that is a
perf report
should always be the line oriented interface, and the newt UI should be
something like
perf treport
Btw, am I the only one that doesn't find the next interface too helpful?
In general the line oriented interface seem to present the information
much better, and in the cases where it gets too complicated the newt
interface doesn't really helper either. A real gtk/qt interface with
a proper tree widget would seem like the more useful interface for that.
next prev parent reply other threads:[~2010-08-21 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 17:45 [GIT PULL 0/2] perf/core improvements Arnaldo Carvalho de Melo
2010-08-21 17:45 ` [PATCH 1/2] perf tools: Add --tui and --stdio to choose the UI Arnaldo Carvalho de Melo
2010-08-21 17:47 ` Christoph Hellwig [this message]
2010-08-21 18:26 ` Arnaldo Carvalho de Melo
2010-08-22 8:20 ` Christoph Hellwig
2010-08-22 14:11 ` Arnaldo Carvalho de Melo
2010-09-13 17:51 ` [tip:perf/core] perf ui browser: Don't use windows, slang is enough tip-bot for Arnaldo Carvalho de Melo
2010-08-21 17:45 ` [PATCH 2/2] perf tools: add test for strlcpy() Arnaldo Carvalho de Melo
2010-08-21 19:15 ` [GIT PULL 0/2] perf/core improvements Ingo Molnar
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=20100821174754.GA10213@infradead.org \
--to=hch@infradead.org \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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