From: Bruce Dawson <bruced@valvesoftware.com>
To: "insight@sourceware.org" <insight@sourceware.org>
Subject: Changing keyboard bindings
Date: Sat, 23 Feb 2013 00:33:00 -0000 [thread overview]
Message-ID: <2AC155A009400B4C8B05D518E4819AEF0719C063@exchange10.valvesoftware.com> (raw)
I'm a long-time Windows developer and I'd like to make Insight easier to use for other long-time Windows developers. Can anybody point me to where I should look in order to try reconfiguring the keyboard bindings (step, run, etc.) to match Visual Studio bindings?
Such a change would have to be optional because I'm sure that the Linux community at large does not value Visual Studio compatibility, but for the initial test version I'm okay with having the change be unconditional.
As an example Run/Continue on Visual Studio are bound to F5, step-over is bound to F10, step-in is bound to F11, etc.
next reply other threads:[~2013-02-23 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 0:33 Bruce Dawson [this message]
2013-02-23 0:52 ` Keith Seitz
2013-02-23 2:00 ` Bruce Dawson
2013-02-23 2:17 ` Keith Seitz
2013-02-26 0:51 ` Bruce Dawson
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=2AC155A009400B4C8B05D518E4819AEF0719C063@exchange10.valvesoftware.com \
--to=bruced@valvesoftware.com \
--cc=insight@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).