From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH v2 1/2] perf hists browser: Support horizontal scrolling with '<' and '>' key
Date: Sun, 9 Aug 2015 13:21:39 +0200 [thread overview]
Message-ID: <20150809112139.GD17069@krava.brq.redhat.com> (raw)
In-Reply-To: <20150809103542.GA3415@danjae.kornet>
On Sun, Aug 09, 2015 at 07:35:42PM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> On Sun, Aug 09, 2015 at 11:30:24AM +0200, Jiri Olsa wrote:
> > On Sun, Aug 09, 2015 at 05:21:01PM +0900, Namhyung Kim wrote:
> > > Currently perf TUI report browser doesn't support horizontal scrolling.
> > > So if terminal width is smaller than the actual contents, there's no way
> > > to see them. This patch adds support horizontal movement by '<' and '>'
> > > keys.
> >
> > nice, I wonder we could also have some way to scroll
> > by the column width.. it might be more eye friendly?
> > would need to try first ;-)
>
> Good suggesion. Please see below..
>
> >
> > I also tried it with SKIP_COLS_STEP=1, and it wasn't bad
>
> OK.
>
> >
> > how about having several scroll step options? like:
> > , . - SKIP_COLS_STEP=1
> > < > - SKIP_COLS_STEP=10
> > CTRL-< > - SKIP_COLS_STEP=columns width
>
> I tried to use CTRL but it seems not working.
>
>
> >
> > we could also bind some of this to regular arrows
> > with SHIFT or CTRL, bacause it's probably the most
> > convenient binding for this
>
> Yes, I agree with you. But I don't know how to bind the arrow keys
> with SHIFT or CTRL to do the thing. So I just changed that < > to
> make SKIP_COLS_STEP = column width.
>
>
> Thanks,
> Namhyung
>
>
>
> From 8e1f0a8be36895f9f37df133dcc8020e123b76e9 Mon Sep 17 00:00:00 2001
> From: Namhyung Kim <namhyung@kernel.org>
> Date: Sun, 9 Aug 2015 19:25:32 +0900
> Subject: [PATCH] perf hists browser: Move to prev/next column start by '<' or
> '>' keys
>
> Jiri said that it'd be more eye-friendly if it can move by column
> widths. So change the keys to do it rather than jumping 10 characters.
> Also add ',' and '.' keys which reside same position in the keyboard to
> move by 1 characters.
I like it ;-)
Tested-by: Jiri Olsa <jolsa@redhat.com>
anyway let's hear some other opinions
thanks,
jirka
next prev parent reply other threads:[~2015-08-09 11:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 8:21 Namhyung Kim
2015-08-09 8:21 ` [PATCH v2 2/2] perf hists browser: Support horizontal scrolling for callchains Namhyung Kim
2015-08-09 9:30 ` [PATCH v2 1/2] perf hists browser: Support horizontal scrolling with '<' and '>' key Jiri Olsa
2015-08-09 10:35 ` Namhyung Kim
2015-08-09 11:21 ` Jiri Olsa [this message]
2015-08-10 15:50 ` Arnaldo Carvalho de Melo
2015-08-10 22:46 ` Jiri Olsa
2015-08-10 22:58 ` Arnaldo Carvalho de Melo
2015-08-10 23:02 ` Jiri Olsa
2015-08-10 23:14 ` Arnaldo Carvalho de Melo
2015-08-10 23:15 ` Jiri Olsa
2015-08-11 20:59 ` Arnaldo Carvalho de Melo
2015-08-12 5:41 ` Namhyung Kim
2015-08-12 9:15 ` Jiri Olsa
2015-08-12 13:17 ` Arnaldo Carvalho de Melo
2015-08-11 2:05 ` Namhyung Kim
2015-08-11 2:00 ` Namhyung Kim
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=20150809112139.GD17069@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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
Powered by JetHome