Re: [gimpwin-users] Running GIMP from Command Line Under Windoze

Tor Lillqvist wrote:

>  Kevin Myers writes:
> > then all is fine and gimp starts up in interactive mode.  But if I
> try:
> > "d:\program files\gimp\bin\gimp" -v
> >
> > or
> > "d:\program files\gimp\bin\gimp" --verbose --console-messages
> >
> > or
> > "d:\program files\gimp\bin\gimp" -n --no-data -b
> '(script-fu-log-process
> > "image018test.tif" "")' '(gimp-quit)'
> >
> > nothing seems to happen with any of these command lines.  Any
> ideas what the
> > problem may be???
>
> gimp.exe is a windowing application. It's stdout and stderr are thus
>
> by default not opened, and the output from --verbose goes
> nowhere. Redirect its output to a file (gimp >gimp.log), or pipe to
> more (gimp | more).
>
> Yes, there could be code in GIMP to check if --verbose or some other
>
> switch that causes output to stdout is present, and in that case
> call
> AllocConsole(). Hmm, except that I am not sure whether doing only
> that
> would help, probably one would also need to freopen stdout to "CON:"
> or
> something after calling AllocConsole()?)
>
> Earlier I used to build GIMP as a console application, and then it
> closed the console unless it was asked to be verbose. (This meant
> that
> there was a console window that opened up when you started the GIMP,
>
> but which immediately closed. A bit confusing.)
>
> --tml
>
>
>
>                    Yahoo! Groups Sponsor
                        ADVERTISEMENT


>
> To Post a message, send it to:   [email protected]
> To Unsubscribe, send a blank message to:
> [email protected]
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Yeah I keep around older versions and that is what happens. Also if it

crashed it leaves error messages in a console window.  Keeping older
versions is a way I track things in case something breaks.

Have Fun,
Sends Steve

P.S. Yes I usually lurk....