Greetings. A new python-fu user here. What is the cleanest way to remove a python-fu script, that you have added, from GIMP? The context is that I have added one for testing purposes and now I want to remove it?
I have never had a python script remain in my GIMP menu after removing it from the plug-ins folder. It could be possible that you have duplicate plug-ins.
To all who helped with this, thanks! It appears this 'stuck' plugin is an issue with Windows Vista. Testing of the same plugin, and GIMP version, on XP does not show this issue.
No if you deleted the script Vista could not resurrect it ..no way
Simply in your vista computer you should have another copy of the script hidden somewhere
But no much place to search must be in one of the plugin folder visible from Edit/Preferences/folder/plugin..no way out
We've spent some effort on getting this sorted out in the current development branch of GIMP (for the Windows-development-savvy users: adding manifest resources to the executables).
Just delete it.
Just delete it.
Delete does not remove....
Thanks for the suggestion but under Windows (Vista... ugh), the entry for the deleted plugin stays in the GIMP menu structure.... Any other thoughts?
Re:Python Script
Did you close GIMP and re-open it?
I have never had a python script remain in my GIMP menu after removing it from the plug-ins folder. It could be possible that you have duplicate plug-ins.
What mahvin says: check Gimp
What mahvin says: check Gimp preferences to find the plugin folders and delete also the duplicate.
Looks like a Vista issue
To all who helped with this, thanks! It appears this 'stuck' plugin is an issue with Windows Vista. Testing of the same plugin, and GIMP version, on XP does not show this issue.
No if you deleted the script
No if you deleted the script Vista could not resurrect it ..no way
Simply in your vista computer you should have another copy of the script hidden somewhere
But no much place to search must be in one of the plugin folder visible from Edit/Preferences/folder/plugin..no way out
It's possible that file
It's possible that file virtualization is kicking in - see http://support.microsoft.com/kb/927387
We've spent some effort on getting this sorted out in the current development branch of GIMP (for the Windows-development-savvy users: adding manifest resources to the executables).