From: Michael Welsh Duggan <md5i@md5i.com>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Has anybody got a tool for manipulating dribble files?
Date: Wed, 12 Oct 2011 22:21:26 -0400 [thread overview]
Message-ID: <874nzd6389.fsf@maru.md5i.com> (raw)
In-Reply-To: <20111012190105.GB2870@acm.acm> (Alan Mackenzie's message of "Wed, 12 Oct 2011 19:01:05 +0000")
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
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:
[-- Attachment #2: dribble.el --]
[-- Type: application/emacs-lisp, Size: 831 bytes --]
[-- Attachment #3: Type: text/plain, Size: 769 bytes --]
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.
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)
next prev parent reply other threads:[~2011-10-13 2:21 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 [this message]
2011-10-13 3:43 ` Stefan Monnier
2011-10-13 3:51 ` Michael Welsh Duggan
2011-10-13 21:05 ` Alan Mackenzie
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=874nzd6389.fsf@maru.md5i.com \
--to=md5i@md5i.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.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.
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.