GIMP Version: 2.10.24
Operating System: Windows
OS Version: Windows 10
GIMP Experience: New User
Hello, I'm having a very unusual problem when experimenting with running a very basic scm script.
I have one version of the script that is this:
(define (script-fu-test)
(gimp-message "no variable TEST!")
)
When I run this code with the command line prompt
gimp-2.10.exe -i -b "(script-fu-test)" -b "(gimp-quit 0)"
it performs as expected, outputting "no variable TEST!" in the GIMP output window, after which it reports that the 'batch command executed succesfully' and then prompts me to press any key to exit. This is all well and good.
However, when I modify the script as such:
(define (script-fu-test strpass)
(gimp-message "no variable TEST!")
(gimp-message (string-append "TEST! with" strpass))
)
and I input the command line prompt
gimp-2.10.exe -i -b "(script-fu-test "stringy thingy TEST")" -b "(gimp-quit 0)"
OR the command line prompt
gimp-2.10.exe -i -b '(script-fu-test "stringy thingy TEST")' -b "(gimp-quit 0)"
then the GIMP output window only reports that the 'batch command executed successfully'; but this is clearly not the case, since if it had executed at all, then it should have written
at least "no variable TEST!" to the GIMP output console!
Further experiments with the command line syntax have done no good: using escape characters as in
gimp-2.10.exe -i -b "(script-fu-test \"stringy thingy\")" -b "(gimp-quit 0)"
causes GIMP to halt, reporting an 'Error: Error reading string'.
I'm not sure what I'm doing wrong here: I've based my code on the example given on the gimp website's basic batch tutorial (I can't post a link as a new user, but it's the first result on Google when searching for "gimp batch processing"), and tried formatting my command line prompt based on examples shown on forums like this one, but my command line doesn't seem to be willing to execute any code to which I'm passing a string, yet it doesn't give me any error messages either, instead acting as though the script executed despite that clearly not being the case.