Working command line arguments fail in shell script

[TimorousMe]

(03-21-2021, 05:59 PM)Ofnuts Wrote: On my Linux, the thing that handles -b "python-fu-eval" is /usr/lib/gimp/2.0/plug-ins/python-eval/python-eval.py, so:

1. The pluginrc file in your Gimp profile should have a line like (plug-in-def "${gimp_plug_in_dir}/plug-ins/python-eval/python-eval.py" 1573315502
   
2. The registration atom in the python file should be python-fu-eval
   

My pluginrc file is saved here "/Users/TimB/library/application support/gimp/2.10" and it includes something very similar to what you describe above, but with a different number (see below). If I properly understand the meaning of "registration atom" then I believe this also has a registration atom of "python-fu-eval."

If I do this in Linux it works fine to launch Gimp from a shell script, but not in OS X. Any ideas?

Code:

(plug-in-def "${gimp_plug_in_dir}/plug-ins/python-eval.py" 1611605883
   (proc-def "python-fu-eval" 1
        "Evaluate Python code"
        "Evaluate python code under the python interpreter (primarily for batch mode)"
        "Manish Singh"
        "Manish Singh"
        "2006"
        ""
        0
       (icon icon-name -1 "")
        ""
        2 0
       (proc-arg 0 "run-mode" "The run mode { RUN-INTERACTIVE (0), RUN-NONINTERACTIVE (1) }")
       (proc-arg 4 "code" "The code to evaluate")))