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:


When I run this code with the command line prompt

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:

and I input the command line prompt

OR the command line prompt

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

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.

Hello,

I don't know Scheme well. I believed that "define" always take only two arguments. Is it the case ? If so, I would think you can fix it by add "begin".

Hope this helps.

Did you try python instead?

https://stackoverflow.com/questions/444 ... 0#44435560

I must be honest: I've spent hours on this already to the point where I've realized Python would be more efficient (went ahead and re-installed Python on my machine even before making this thread), but I'm also so frustrated by script-fu/scheme that I really want to "beat" this issue, efficiency be damned. I was hoping there was a simple fix that more experienced folks would be able to help me with, but if this is a really arcane problem I will just give up on the script-fu side of things and jump to Python.

Give this a try:


and use the escaped double-quotes version of the command line.

I tried this, but it's reproducing the same odd behavior of the initial script, either failing to work due to bad or missing arguments, or else "successfully" running without even executing the unappended gimp-message function.

Works perfectly for me:





Be careful that you haven't created two versions of script-fu-test as all scripts share the same name-space and if you've got a second version it will overwrite the first in memory, but how the overwrite happens will depend on which order the files are loaded.

If you are on windows you shouldn't install Python (or at least be very careful). AFAIK installing Python after Gimp breaks the Python support in Gimp (which comes with its own Python which conflicts with the one installed separately). Things can possibly work if you install Python first and then Gimp.