On 12/9/18 7:50 PM, Gary Aitken wrote:
In the past I have interactively batch processed images via a shell
script
that invokes gimp for each image. This is both inconvenient and slow.
Inconvenient because there are parameters I need to enter into some
python-fu
scripts that are the same for e
On 12/9/18 4:38 PM, Bob Long wrote:
Gary Aitken wrote on 10/12/18 4:50 am:
...
Is there a way to do one of the following:
A. Start gimp with a list of file names to process, and have it
load only the first on the list. Then when one quits or closes the
image, load the next one, etc?
B. I can
Gary Aitken writes:
> In the past I have interactively batch processed images via a shell script
> that invokes gimp for each image. This is both inconvenient and slow.
> Inconvenient because there are parameters I need to enter into some python-fu
> scripts that are the same for each of the image
Gary Aitken wrote on 10/12/18 4:50 am:
> In the past I have interactively batch processed images via a shell
> script
> that invokes gimp for each image. This is both inconvenient and slow.
> Inconvenient because there are parameters I need to enter into some
> python-fu
> scripts that are the sam
In the past I have interactively batch processed images via a shell script
that invokes gimp for each image. This is both inconvenient and slow.
Inconvenient because there are parameters I need to enter into some python-fu
scripts that are the same for each of the images, and slow because of the
