Hmmm, I wonder why using the --batch option wasn't suggested when I ran into
the problems that I mentioned previously...

Unfortunately, it has been so long ago now that I don't remember the
details.  I gave up trying after a couple of days of trial and error plus a
number of related emails.  I can't think of any reason at this point why
that wouldn't have been a reasonable solution.


----- Original Message ----- 
From: "Simon Budig" <[EMAIL PROTECTED]>
Sent: Friday, March 19, 2004 9:59 PM
Subject: Re: PDB named and default parameters (was Re: [Gimp-developer]
TheMark Shuttleworth offer)

> Kelly Martin ([EMAIL PROTECTED]) wrote:
> > Kevin Myers wrote:
> > > Admittedly, the Windows command prompt (not simply Explorer) is less
> > > capable than most *nix command shells.  However, there are also a
> > > very large number of Windows based GIMP users, and one of the
> > > requirements of GIMP 2.x is that it should be as usable under Windows
> > > as it is on other operating systems.
> >
> > Windows inhibits its own usability in this respect.  It is nearly
> > impossible to get imbedded quotes from the Windows command line.  This
is a
> > defect in the Windows shell.  Getting around it would force us to use
> > weird character for string quoting, which would be confusing to
> > In my opinion, the sacrifice is not worth the gain: we should not have
> > do something Weird and Bizarre to cope with Microsoft's inferior
> Also please consider, that scripting from the commandline is not the
> thing the average Windows- (and even Linux-) user needs. If a windows
> user really needs scripting, I'd recommend to install e.g. a bash.
> The other option always is to use  "gimp-1.3 --batch -" and pass
> the commands to execute to stdin.
> Bye,
>         Simon
> -- 
> _______________________________________________
> Gimp-developer mailing list

Gimp-developer mailing list

Reply via email to