Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!oberon!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.emacs
Subject: Re: Keyboard macros (was: Re: Copy From Above?)
Message-ID: <15447@oberon.USC.EDU>
Date: 19 Feb 89 08:52:13 GMT
References: <690026@hpsemc.HP.COM> <36077@bbn.COM> <50884@yale-celray.yale.UUCP> <36476@think.UUCP>
Sender: news@oberon.USC.EDU
Reply-To: blarson@skat.usc.edu (Bob Larson)
Organization: USC AIS, Los Angeles
Lines: 22

In article <36476@think.UUCP> barmar@kulla.think.com.UUCP (Barry Margolin) writes:
>In article <50884@yale-celray.yale.UUCP> Ram-Ashwin@cs.yale.edu (Ashwin Ram) writes:
>>I wish there was a way of "decompiling" the macro, i.e., a function that
>>inserted, not the raw keystrokes, but the names of the commands that those
>>keytrokes were bound to.

>The problem is that it's
>difficult to know the binding of a keystroke, because previous
>commands might have caused key bindings to change.

I consider this a bug in the way Gnu Emacs handles keyboard macros.
Mg saves the functions that have been executed (and argument strings)
rather than the keys pressed to get the result.  (Other than minor
twiddling -- self-inserted characters are merged into a call to insert,
etc.)  Decompile keyboard macro will probably be in the same release
of mg as an extention languages.  (Most likely 3a.)

-- 
Bob Larson	Arpa: Blarson@Ecla.Usc.Edu	blarson@skat.usc.edu
Uucp: {sdcrdcf,cit-vax}!oberon!skat!blarson
Prime mailing list:	info-prime-request%ais1@ecla.usc.edu
			oberon!ais1!info-prime-request