Re: [gimpwin-users] Running GIMP from Command Line Under Windoze
"Kevin Myers" <[email protected]>
| Newsgroups | gmane.comp.video.gimp.windows.devel |
|---|---|
| Message-ID | <00a501c27886$9b215940$66c8a8c0@gusher> |
Hi Tor - I hadn't even remotely considered the possibility of re-directing the output to a file. Thanks! That's a great tip. Sure wish I had thought of that. Might be nice to document that somewhere, along with the following tidbit... In the meanwhile, Jernej Simoncic send me a small utility that allows one to very easily turn the console window back on for a Win 32 non-console application. I applied this to the gimp executable, and it works great. I am now seeing all of the messages. Some of them related to script-fu aren't very descriptive, but they are sure a whole heck of a lot better than nothing at all! Anyway, thanks once again for your reply. Regards, s/KAM ----- Original Message ----- From: "Tor Lillqvist" <[email protected]> To: <[email protected]> Cc: <[email protected]> Sent: Sunday, October 20, 2002 5:21 PM Subject: [gimpwin-dev] [gimpwin-users] Running GIMP from Command Line Under Windoze > 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 > > > > > 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 http://docs.yahoo.com/info/terms/ > >