Gimp-Forum.net
Missing script-fu "refresh scripts" submenu - Printable Version

+- Gimp-Forum.net (https://www.gimp-forum.net)
+-- Forum: GIMP (https://www.gimp-forum.net/Forum-GIMP)
+--- Forum: Gimp 2.99 & Gimp 3.0 (https://www.gimp-forum.net/Forum-Gimp-2-99-Gimp-3-0)
+--- Thread: Missing script-fu "refresh scripts" submenu (/Thread-Missing-script-fu-refresh-scripts-submenu)

Pages: 1 2

RE: Missing script-fu "refresh scripts" submenu - rich2005 - 07-02-2025

Quote: "I ran the test with the same file as you (quick-save-web the .scm) saved in the Gimp scripts directory"

Same as Ofnuts. Put the file in its folder in your User Profile plug-ins folder. Now a requirement that plug-ins go in their own folder (and are executable in linux)

RE: Missing script-fu "refresh scripts" submenu - Frenchie - 07-03-2025

(07-02-2025, 07:56 PM)Ofnuts Wrote:
(07-02-2025, 06:39 PM)Frenchie Wrote:
(07-02-2025, 01:53 PM)rich2005 Wrote: Works here. A simple observable example.     https://i.imgur.com/d8NMTRX.mp4

I ran the test with the same file as you (quick-save-webp.scm) saved in the Gimp scripts directory:
- Open a Gimp 3.0 session
- Open an image file
- Run quick-save-webp from the Tools menu
- Edit the quick-save-webp.scm file with NotePad
- Save the file
- Run quick-save-webp from the Tools menu
The last update in quick-save-webp.scm file was not taken into account (it only happens if I close Gimp).
One clarification: I'm using a Windows 10 PC.

If it's in the scripts directory then it is a script. To work as a plugin it should be in the plug-ins directory.
I tried putting the quick-save-webp.scm file in the plugins directory, but the quick-save-webp function was no longer present in the Tools menu.
I just ran another test, this time creating a quick-save-webp subdirectory in the plugins directory and moving the quick-save-webp.scm file there.
It works!!!
There's probably a reason why the "Refresh Scripts" option was removed in Gimp 3.0. I'll miss it.
Thanks again, ofnuts, rich2005, and MrsP-from-C.
Postscript: I just saw richie2005's answer "Put the file in its folder". I came to this solution by comparing with existing plugins.