houghi <houghi@[EMAIL PROTECTED]
> writes:
>> Another way of debugging your scripts is turning tracing on, by issuing
>> (tracing TRUE), so, for instance:
>>
>> gimp -ic -b "(begin (tracing TRUE) (your code ... ) (gimp-quit
>> RUN-NONINTERACTIVE))"
>>
>> and you can turn it off with (tracing FALSE).
>
> OK. This becomes interesting.
Ehm, wait, apparently this does not seem to work in real batch mode
(only in gimp -i -b - , i.e. reading from standard input, effectively
giving a REPL, which is also what I use in gimp-mode).
So if you want to debug your scripts, run, i sequence,
gimp -i -b -
(tracing 1)
(the pieces of code that you would rather like to give as a shell
argument...)
> I will give feedback later on how things went. With your permission, I
> will put the information online as well. I willeven try to get it on
> docs.gimp.org if you allow me.
Sure, this is free information, as knowledge always should be. Just
make sure it is correct and do not mention my name ;)
Niels.
|
