GIMP Version: 2.8.10
Operating System: Linux
GIMP Experience: Beginner Level

---

Say create a heading MyFavFilters and put your favourites under there instead of having to dig through the various menus?
Is there some file I can edit?

for .scm scripts and .py scripts it's quite easy:
- edit your script with a text editor like notepad++ for instance
- change the menu entry you find in one you better prefer
(this is one of my menu entries, as an example:
menu='<Image>/Addons/AddPY/Render/Fill grid with random color/')
- close, reopen gimp
you will find your filter where you said

A method that works with all, is to create a short script that calls your favorite one and registers it wherever you want. You can have one single script to relocate all your scripts/plugins (scheme, python or C/C++). This also doesn't require to re-edit the script/plugin each time you download a new version.

But IMHO, the ones you use really often should be assigned to keyboard shortcuts, and don't forget Ctrl-F & Ctrl-Shift-F to re-execute the last filter (with same or new parameters).

@ Dinasset - I already do that with scripts I have downloaded.
@ Ofnuts Yes I have assigned a few keyboard shortcuts.

Do you mean ofnuts?

@molly i only meant ofnuts for the second comment - I have edited my post

Wow, it's fantastic!
But in my ignorance about that, I ask you Ofnuts: how does it look like such a script?
Could you post a simple example: a script which calls just one other script and changes its registration menu, for instance under "my preferred filters"?

Here's how I suggested doing this: viewtopic.php?f=4&t=9942&p=129925&hilit=register#p129925

Kevin

Thanks a lot, Kevin!
I forgot that extremely useful posting.
Can it be used for ANY kind of filter (scheme - python - exe) as Ofnuts says?

just another (silly) question, KP:
- the sample you provided in the referenced post should have itself a "registration"? or just putting those lines (with adjusted filters names) as an zzz.scm at the end of the opened scripts is enough? question obsolete

edit: re-reading that post it seems that it is enough to put it as the last .scm so it is

2.nd edit: applied KP suggestion, it works perfectly; very easy to do that way

3.rd edit: a little warning to those who like to try the same: the original script MUST have the menu registration defined in a separate line, like script-fu-menu-register ...(new style), NOT as a line embedded in the script registration (old style)

Old question, which today enters again the game.
I used in the past (and also today) this technique to "move" a script-fu from one menu to another one
My specific question is:
- what to specify in a line referring to a compiled C filter?
not being a "script-fu" I tried to enter the command which is used in the C code, that is:
(gimp-plugin-menu-register... ) instead of (script-fu-menu-register... )
but it's not accepted, neither if entered with underscores (as in C code) nor if entered with dashes
last attempt: (gimp-plugin-menu-register "plug-in-liquify" "<Image>/BestFilters/Distorts")
tried also with additional parenthesys:
(gimp-plugin-menu-register ("plug-in-liquify" "<Image>/BestFilters/Distorts"))
it still tries to find the entry in script-fu-menu-register and doesn't find it
For someone who can make the correct line statement work, the plug-in I'd like to move is
liquify ("plug-in-liquify"), as in the attempt shown
note: the command with a script-fu filter works fine (provided it has been defined with a specific separated menu-register command)

If you investigate the GIMP source code, you find that gimp-plugin-menu-register is only allowed to be called by the plug-in itself, no-one else is allowed to call it.

What ofnuts suggested is to write a script-fu/python wrapper round a call to the plug-in, then you can register the script-fu/python anywhere you want to.

Oh, I see! A wrapper...
Now it's clear.
Thanks Kevin, I tought it could be possible to use your technique...(not only for script-fu I mean)

(for the moment, I'm not oriented to use a wrapper; once you have that for each filter you will have two entries; the original entry under the original menu and the wrapper entry under the wrapper menu)

You could just change the pluginrc file menu entry.

Yes Rod, it has been my preferred solution so far.
I was just looking at the possibility to have a "menu-changer" script like for the script-fus, but I will stay with the pluginrc solution.
Thanks