From: Jim Wilson 
@Date: Mon, 24 Feb 2003 12:20:04 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



At 10:19 AM 2/24/2003, you wrote:
>What you say is correct, but I can't do that most of the time.
>If I were to select "Execute" from the menu presented after a
>successful compile, the macro would run against (process) the
>macro's own code itself, which isn't what I need.  I have to
>select cancel at that menu, then switch to the buffer/file that
>I want to run the macro against, and then Ctrl-X, macroname to
>run the macro then.
>
>Under those circumstances, it seems to be running the loaded
>macro code from the previous compilation.  At least I only get
>good/changed results if I first purge the macro from the
>macro, purge menu.
>
>I've been trying to think through the logic of it, and perhaps
>it is something that just has to be, or something else will
>break?
>
>What brought it up was a simple macro to strip leading whitespace
>and ">" characters from text, as the first step in cleaning up
>e-mail message text that has been quoted and re-wrapped a couple
>of times.  It didn't work right the first time, so I re-did it.
>If I had selected "Execute" from the post-compilation message,
>it would have stripped the leading whitespace from the macro's
>own code.  Hitting cancel and then executing the revised macro
>against the message body text doesn't seem to execute the revised
>macro code unless I first purge the macro using the macro, purge
>menu.

My experience duplicates this precisely. Execute does seem to purge first, 
but that only works for certain circumstances, where PurgeMacro works 
(seemingly) under all circumstances.


Regards,
Jim

--
TSEPro Mailing List
List Maintenance: www.semware.com/html/list.htm



---
[sawasdi.apana.org.au] (3:800/846.13)