To get at your new script-fu you need to do the following:
1. Place the text file (my-new-script-fu.scm) in your own .gimp/scripts
In my case, it's ~/.gimp-1.2/scripts
2. In the gimp, go to <Toolbox>/Xtns/Script-Fu/Refresh to force a reload of
That should do it.
If problems arise, check (a) where you registered the script; (b) that there
are no leftover editor backup files lying around; and (c) that your scheme
code has all its proper parentheses and doesn't contain errors.
I have discovered that after long edit/test sessions with a new script that
things often work better if I restart the GIMP.
If your script-fu is actually a perl-fu, one does it differently. Perl
scripts are traditionally saved in the ~/.gimp-1.2/plug-ins directory, and to
test them from your favorite text editor you need to start the gimp's perl
server (<Toolbox>/Xtns/Perl/Server), after which you can run the perl script
from the command line in your editor. I have discovered that editor backup
files for perl scripts in the plug-ins directory do get loaded as plug-ins,
and may (nay, probably will) mess up your debugging sessions. So make sure no
old backup files are left lying around.
I have also noticed problems when working with perl -- if the new
plugin/script complains about something really strange like a color being bad
or anything else that seems really off the wall, go into the <Toolbox>
/Xtns/Parasite_Editor and delete the entry corresponding to the misbehaving
plug-in. This happens usually when I have changed something in the interface
and the parasite contains saved values from the previous version.
Jeff Trefftzs <[EMAIL PROTECTED]>
http://www.tcsn.net/trefftzs Home Page
http://gug.sunsite.dk/gallery.php?artist=68 Gimp Gallery
http://trefftzs.topcities.com/home.html Photo galleries
Gimp-user mailing list