On Sat, Nov 26, 2005 at 11:52:09AM -0800, Robert Kleemann wrote:
>
> (plug-in-path "/home/robert/custom-plug-ins:/usr/lib/gimp/2.0/plug-ins")
>
> The directories will probably change when the gimp version changes but
> since the scripts will likely have to be changed as well it's not a big
> de
Thanks Yosh for the definitive answer. I've never looked at the gimp's
code base so that would be a huge effort for me to fix this small problem.
I tried Carol's solution of a custom gimprc and that seems to be a good
enough solution. In order to get it to work I had to first load the
standa
On Mon, Nov 21, 2005 at 05:33:22PM -0800, Robert Kleemann wrote:
> michael chang wrote:
> >perl scripts with the GIMP module can be loaded just like any
> >executable script; for example, if I have a script that uses GIMP
> >called myfile.pl and I go to that directory and call ./myfile.pl, it
> >wi
michael chang wrote:
perl scripts with the GIMP module can be loaded just like any
executable script; for example, if I have a script that uses GIMP
called myfile.pl and I go to that directory and call ./myfile.pl, it
will run.
Thanks for the idea. I never thought of running the script as a
On Mon, Nov 21, 2005 at 12:44:38PM -0800, Robert Kleemann wrote:
> Is it possible to have gimp run a script that located in an arbitrary
> directory? It seems that gimp wants to run scripts from
> ~/.gimp-n.n/[plug-ins|scripts]/
>
File-->Preferences
there is an expander twisty for folders. fro
On 11/21/05, Robert Kleemann <[EMAIL PROTECTED]> wrote:
> Is it possible to have gimp run a script that located in an arbitrary
> directory? It seems that gimp wants to run scripts from
> ~/.gimp-n.n/[plug-ins|scripts]/
> 2) It only works for scripting languages where white space is not
> signifi
