Addendum:
-
You might have to add a "exit" at the end of your script in order
for the console to close after the script.
-
I've had problems using this syntax when I did not add an empty
line at the end of the script (because it would not do the “enter” on the
exit line)
-
Just to make sure it was clear, you have to use the word "type" in
the command, so in your example, it would be:
type temp.anymcr | anybodycon
Good luck 
Jean-Olivier
From: anyscript@yahoogroups.com [mailto:anyscript@yahoogroups.com] On Behalf
Of Jean-Olivier Racine
Sent: Thursday, November 01, 2007 8:34 AM
To: anyscript@yahoogroups.com
Subject: RE: [AnyScript] Re: calling a macro from the command line, change
from v2 to v3?
Importance: High
Hello David,
I’d like to suggest a workaround for your problem. Instead of typing
“anybodycon <scriptname>”, try using the redirection pipe and use the
following syntax: “type <scriptname> | anybodycon”. This should yield the
exact same result.
Hope it helps,
Jean-Olivier
From: anyscript@yahoogroups.com <mailto:anyscript%40yahoogroups.com>
[mailto:anyscript@yahoogroups.com <mailto:anyscript%40yahoogroups.com> ] On
Behalf
Of AnyBody Support
Sent: Wednesday, October 31, 2007 8:50 AM
To: anyscript@yahoogroups.com <mailto:anyscript%40yahoogroups.com>
Subject: [AnyScript] Re: calling a macro from the command line, change from
v2 to v3?
Importance: High
Dear David,
You are perfectly right that something is wrong. It is simply a bug.
It has been located and fixed. I am embarrased that this slipped
through our testing procedures.
We shall release the fix as soon as possible. Let us know if you need
the fix very urgently, then I can upload a temporary fix here on the
group.
Best regards,
Michael
AnyBody Support
— In anyscript@yahoogroups.com <mailto:anyscript%40yahoogroups.com>
<mailto:anyscript%40yahoogroups.com> ,
“dww805” <dwwagner@…> wrote:
>
> I was using anybody v2 with the following command:
>
> anybodycon temp.anymcr
>
> where temp.anymcr is an anybody macro.
>
> However, I have ugraded to v3, and when I make the same call, the
macro does not get
> loaded in (and run) but I get put straight into the user interface
(command line) where I can
> type in commands like ‘run’, ‘load’, and even
‘runmacro(“temp.anymcr”)’ => in which case the
> macro does run.
>
> Have you encountered this problem before? Am I doing something
wrong here?
>
> Thank you in advance.
>
> -David
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]