Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!its.rpi.edu!tale From: tale@its.rpi.edu (David C Lawrence) Newsgroups: comp.emacs Subject: Re: Keyboard macros (was: Re: Copy From Above?) Message-ID: Date: 16 Feb 89 20:46:14 GMT References: <690026@hpsemc.HP.COM> <36077@bbn.COM> <50884@yale-celray.yale.UUCP> Sender: usenet@rpi.edu Reply-To: tale@pawl.rpi.edu Organization: The Octagon Room Lines: 27 In-reply-to: Ram-Ashwin@cs.yale.edu's message of 16 Feb 89 17:23:24 GMT 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. Keyboard macros are neat for simple things, but if you want to modify one you're out of luck. For most purposes I basically dislike any Emacs which isn't GNU; I'm very used to using many, many features of GNU Emacs and know its syntax and functions much better than MicroGnu or Prime's Emacs. Prime Emacs, however, does what you want. Rather than simply doing an fset to the string which would execute tha macro if typed, it will expand the macro to its PEEL (like LISP, but much worse) equivalent. You can then make modifications as needed. This of course helps little for what you want from GNU. macros.el is not a very large file at all; I think it would be quite possible to build a skeleton defun from the keymap definitions for the macro. The difficulty is in knowing how (interactive) is being called by each function. I would be willing to find a way to do this, but it on't be any time real soon. If no one else does it, I'll put it on my list fof things to do (around April or so ... ugh). Dave -- tale@rpitsmts.bitnet, tale%mts@rpitsgw.rpi.edu, tale@pawl.rpi.edu