From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING][PATCH] Add shortcuts for "nexti" and "stepi" commands in Single-Key mode
Date: Fri, 04 Aug 2017 05:48:00 -0000 [thread overview]
Message-ID: <CAHEcG95BWOsOtnVEyfsV3=WNqCb90nKYbbt9CC085xaM8v4c3g@mail.gmail.com> (raw)
In-Reply-To: <ba695030652f117eb780ce4e1ba23685@polymtl.ca>
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
On 27 July 2017 at 12:25, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> On 2017-07-27 11:11, Ruslan Kabatsayev wrote:
>>>
>>> I was thinking that perhaps that when focusing...
>>>
>>> a source view: s/n do source line stepping, S/N do assembly stepping
>>> an asm view: s/n do assembly stepping, S/N do source line stepping
>>>
>>> Basically, they would switch role. Is that too confusing?
>>
>> This might be OK, but what if current focus in on registers window?
>> Disable all single-key stepping?
>
>
> Indeed. And when the user is in the "Source + Asm + Prompt" configuration
> and the prompt is focused, what would we do? That's perhaps a good idea in
> theory, but it would need to be more thought through.
>
> You patch provides a predictable behavior across all modes, so I don't think
> we can go wrong with that.
>
> Simon
next prev parent reply other threads:[~2017-08-04 5:48 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 [this message]
2017-08-04 13:29 ` Simon Marchi
2017-08-04 19:11 ` Ruslan Kabatsayev
2017-08-04 21:04 ` John Baldwin
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='CAHEcG95BWOsOtnVEyfsV3=WNqCb90nKYbbt9CC085xaM8v4c3g@mail.gmail.com' \
--to=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