From: Alan Mackenzie <acm@muc.de>
To: Michael Welsh Duggan <md5i@md5i.com>
Cc: emacs-devel@gnu.org
Subject: Re: Has anybody got a tool for manipulating dribble files?
Date: Thu, 13 Oct 2011 21:05:57 +0000 [thread overview]
Message-ID: <20111013210557.GB3412@acm.acm> (raw)
In-Reply-To: <874nzd6389.fsf@maru.md5i.com>
Hi, Michael.
On Wed, Oct 12, 2011 at 10:21:26PM -0400, Michael Welsh Duggan wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > Hi, Emacs.
> > I've got a rather largish dribble-file (thanks Michael!) for recreating
> > a bug. Does anybody here have or know about a tool which can replay
> > (partially or wholly) such a file, or anything similar?
> I asked this a little while ago, and got no response. So I wrote the
> following function:
[ .... ]
Excellent man!
> This function reads a dribble file and creates a keyboard macro from
> it. It is heuristic in nature. You cannot tell the difference between
> `RET' being pressed and the key sequence "<return>" in a dribble file,
> along with a couple of other similar things.
OK.
> Once you have the macro, it can then be edited using M-x edit-kbd-macro
> (of `C-x e'). Unfortunately, the macro will stop on any C-g or any
> command that raises an error, so the macro must be edited to elide
> these.
> In this particular case, I have done the work, and I will be posting an
> exact recipe for recreating the problem in Bug 9560. (Once nice thing
> about using a keyboard macro to replicate the problem is that you can
> trim it to look at intermediate state.)
:-)
> --
> Michael Welsh Duggan
> (md5i@md5i.com)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2011-10-13 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 19:01 Has anybody got a tool for manipulating dribble files? Alan Mackenzie
2011-10-13 2:21 ` Michael Welsh Duggan
2011-10-13 3:43 ` Stefan Monnier
2011-10-13 3:51 ` Michael Welsh Duggan
2011-10-13 21:05 ` Alan Mackenzie [this message]
2011-10-13 2:23 ` Stefan Monnier
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=20111013210557.GB3412@acm.acm \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=md5i@md5i.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.