d5a83429b4
Why: 1) users can install .scm scripts to plug-ins dir 2) Crashing scripts do not crash extension-script-fu Scripts (.scm files) have a shebang and are executable and in a same-named subdir of plugin dir. Interpreter/scripts create PDB procs of type PLUGIN unlike extension-script-fu which creates PDB procs of type TEMPORARY, owned by extension-script-fu. Unlike other interpreters, the interpreter is-a plugin outright, not by virtue of the script subclassing GimpPlugin and using GI. More details in /plug-ins/script-fu/interpreter/README
25 lines
705 B
Scheme
25 lines
705 B
Scheme
#!/usr/bin/env gimp-script-fu-interpreter-3.0
|
|
|
|
; Test a .scm file that does not call script-fu-menu-register
|
|
; The menu will NOT default.
|
|
; Expect "Test SF interpreter 4" to NOT EXIST in any menu
|
|
; Expect the PDB proc "script-fu-test4" does appear in the PDB Brower
|
|
|
|
; Two test cases:
|
|
; Alongside an executable script: plug-ins/test4/test4.scm NOT executable
|
|
; Executable, in its own directory: plug-ins/test1/test4.scm is executable
|
|
|
|
(define (script-fu-test4)
|
|
(gimp-message "Hello script-fu-test4")
|
|
)
|
|
|
|
(script-fu-register "script-fu-test4"
|
|
"Test SF interpreter 4"
|
|
_"Just gives a message from Gimp"
|
|
"lkk"
|
|
"lkk"
|
|
"2022"
|
|
"" ; all image types
|
|
)
|
|
|
|
; !!! No call to script-fu-menu-register
|