From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
Ruslan Kabatsayev <b7.10110111@gmail.com>
Subject: Re: [PING][PATCH] Add shortcuts for "nexti" and "stepi" commands in Single-Key mode
Date: Fri, 04 Aug 2017 21:04:00 -0000 [thread overview]
Message-ID: <11715373.GM5IrkgxOV@ralph.baldwin.cx> (raw)
In-Reply-To: <2085ccb4878f1acccefb8aa2312f7c34@polymtl.ca>
On Friday, August 04, 2017 03:29:01 PM Simon Marchi wrote:
> On 2017-08-04 07:48, Ruslan Kabatsayev wrote:
> > Hello,
> >
> > After using these shortcuts for some time I found that they are still
> > not best: one has to hold Shift in order to continuously step in
> > instruction mode. Would it be better to e.g. replace N->m, S->z? I
> > think we can basically use any non-occupied shortcuts here, they just
> > should be convenient, not necessarily be associated with "long"
> > version of the commands.
> >
> > Regards,
> > Ruslan
>
> Ok, I understand how having to hold shift may not be so practical.
>
> It would be nice if there was a pattern that made it easy to
> remember/deduce the keys for stepi/nexti from the keys for step/next,
> which are more obvious. For example, if we used 'a' for stepi and 'b'
> for nexti, the "instruction" versions of the keys would both be at the
> left of their "non-instruction" counterpart. That's with a
> QWERTY-centric view though, maybe it doesn't make sense with other
> layouts.
I agree it should be something deducible like a/b or d/m.
--
John Baldwin
prev parent reply other threads:[~2017-08-04 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 6:13 [PATCH] " Ruslan Kabatsayev
2017-07-13 15:59 ` Eli Zaretskii
2017-07-13 18:19 ` Ruslan Kabatsayev
2017-07-13 19:04 ` Eli Zaretskii
2017-07-13 19:09 ` Ruslan Kabatsayev
2017-07-13 19:41 ` Eli Zaretskii
2017-07-26 19:19 ` [PING][PATCH] " Ruslan Kabatsayev
2017-07-26 20:53 ` Simon Marchi
2017-07-27 6:00 ` Ruslan Kabatsayev
2017-07-27 8:19 ` Simon Marchi
2017-07-27 9:12 ` Ruslan Kabatsayev
2017-07-27 9:27 ` Simon Marchi
2017-08-04 5:48 ` Ruslan Kabatsayev
2017-08-04 13:29 ` Simon Marchi
2017-08-04 19:11 ` Ruslan Kabatsayev
2017-08-04 21:04 ` John Baldwin [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=11715373.GM5IrkgxOV@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=b7.10110111@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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