From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Intercept and handle Delete/Home/End keys in the TUI
Date: Wed, 10 Jun 2015 15:28:00 -0000 [thread overview]
Message-ID: <5578579F.6040903@redhat.com> (raw)
In-Reply-To: <CA+C-WL-F5=6T0bczZNRMVSaJ9yB_g4zXg6w5PJQ4TpLeaZ_Lnw@mail.gmail.com>
On 06/04/2015 12:55 AM, Patrick Palka wrote:
> On Wed, Jun 3, 2015 at 7:28 PM, Patrick Palka <patrick@parcs.ath.cx> wrote:
>> These keys are mapped by wgetch() to special ncurses-specific values and
>> are otherwise passed through to readline, to no useful effect.
>>
>> This patch intercepts these keys in the TUI and gives them their
>> expected function.
>
> The commit message is slightly misleading. These keys work as
> expected when the command window is in focus. But when another window
> is in focus, these keys currently have no function. This patch gives
> them their expected function when the command window is not in focus.
I'd think it very natural that given that Up, Down, Left, Right, PageUp/PageDown
all scroll the source window, so should Home/End. When the console window is
not on focus, we can use ctrl-a / ctrl-e to move to start/end of line,
just like we use ctrl-p/ctrl-n to go "up/down" in history.
>
> Alternatively when the command window is not in focus the Home and
> Delete keys could be given the function of scrolling the source/disasm
> windows all the way up or down.
Yes, that.
> Personally I don't think that is very useful. I think the traditional binding
> would probably see more use.
I do not agree. I know I'd give lots of use to Home jumping to the
start of the file myself.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-06-10 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 23:29 Patrick Palka
2015-06-03 23:55 ` Patrick Palka
2015-06-10 15:28 ` Pedro Alves [this message]
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=5578579F.6040903@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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