From: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] questions about Emacs/camldebug
Date: Sun, 6 Dec 2015 20:54:26 +0100 [thread overview]
Message-ID: <56649272.1090000@gmail.com> (raw)
Dear all,
Are there people who use camldebug in Emacs?
What do you think about it?
Do you employ some custom tricks to make the invocation more seamless?
Now, when I want to run it, I need to do this:
M-x camld<TAB> (* 7 keystrokes *)
<BACKSPACE>...<BACKSPACE>program (* 19 keystrokes *)
C-x C-o (* switching to the buffer above that holds the source code ... 2-keystrokes
C-x C-a C-b (* set a breakpoint at the current cursor's position ... 3-keystrokes *)
C-x C-a C-r (* run the program ... 3-keystrokes *)
------------------------------------------------------------------------------------------------------------------
(* 34 keystrokes *)
Did somebody succeed in making this less verbose?
Would it be possible to define some macro that would do all this which I could bind to a single key? (e.g. F12 or whichever else).
Thank you in advance for any kind tips.
reply other threads:[~2015-12-06 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56649272.1090000@gmail.com \
--to=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).