On Sun, Apr 09, 2006 at 09:34 -0700, saulgoode@brickfilms.com wrote:

Kovacs,

Output from Script-fu can be sent to "stdout" by first performing a:

(gimp-message-set-handler 1)

and then sending your strings using something like

(gimp-message "foobar")

where "foobar" is the string to printed on "stdout".

Perhaps this will be sufficient for your needs?

Yes, definitely! Thank you very much!

(P.s.: as a "keep it stupid and simple" fan I'd probably arrange things in a way that the default print methods of siod do print to stdout. But anyways, what I really needed is just any method to print, so I'll do with what you showed.).

Thanks, Baldvin

saulgoode@brickfilms.com wrote:

Output from Script-fu can be sent to "stdout" by first performing a:

(gimp-message-set-handler 1)

The Procedure Browser shows that the arguments '1' has an equivalent (C style) name of GIMP_CONSOLE. In Script-Fu you remove the leading GIMP_ from named constants shown in the Procedure Browser and change any remaining _ to -. That would mean you could use

(gimp-message-set-handler CONSOLE)

which has the extra benefit of being more readable. You don't have to go back to the procedure browser to find out what the 1 means.

Just a suggestion to use the named constants where available to make the scripts a little more readable, save some trips back to the procedure browser which should make any needed debugging a little less tedious.