[gimpwin-users] Running GIMP from Command Line Under Windoze
Tor Lillqvist <[email protected]>
| Newsgroups | gmane.comp.video.gimp.windows.devel |
|---|---|
| Message-ID | <[email protected]> |
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