option /o:- opens a new window, not stdout

bmerkle · Post by **bmerkle** » Fri Dec 21, 2007 2:31 am

Hi there

i am using /f /o:- as command line option and it works cool.
the only problem is: /o:- opens a _new_ windows.

The description says /o:- should output it to stdout.
However opening a _new_ window is not stdout.

background: I want to use this on a build server and opening new windows etc is a killer there as it runs as services.

a simple workaround is to redirect into a file which works, however stdout output would be appreicated.

thanks
Bernhard.

Post by **psguru** » Fri Dec 21, 2007 9:40 am

I can't reproduce this. When I run something like

Code: Select all

examdiff ..\test\1 ..\test\2 /f /o:-

the output goes to the standard out. What OS are you using? Is it Win9x?

bmerkle · Post by **bmerkle** » Fri Jan 04, 2008 6:22 am

psguru wrote:I can't reproduce this. When I run something like
Code: Select all
examdiff ..\test\1 ..\test\2 /f /o:-
the output goes to the standard out. What OS are you using? Is it Win9x?

Hi, no it is WinXP, SP2.

If I invoke the command you gave i also get a _new_ window with the following output which is below: (so you can see it opended a _new_ console).

To use the examdiff tool, e.g. in an automatic build, I need the output in the same console as I am running the examdiff invocation.
It should _not_ open a new console. (and also wait for a user key press)

--> output of your command
File or directory ..\test\1 does not exist
Press any key to close this console window...

thanks,
Bernhard

Post by **psguru** » Fri Jan 04, 2008 3:48 pm

If I invoke the command you gave i also get a _new_ window with the following output which is below: (so you can see it opended a _new_ console).

Unfortunately, there's no screenshot referenced in your post.

You are not, by any chance, using examdiff.exe in the command line instead of examdiff, right?

The other possibility is that for some reason, perhaps because of your user permissions, _wfreopen calls (that EDPro uses to connect to the existing console's standard input, output and error streams) fail. In such case EDPro would fall back to creating a new console.

bmerkle · Post by **bmerkle** » Mon Jan 07, 2008 4:34 am

psguru wrote:
If I invoke the command you gave i also get a _new_ window with the following output which is below: (so you can see it opended a _new_ console).
Unfortunately, there's no screenshot referenced in your post.

You are not, by any chance, using examdiff.exe in the command line instead of examdiff, right?

ah, the behaviour happens with examdiff.exe
If I invoke examdiff.com everything works fine. thanks for the hint.

what is the difference between *.exe. and *.com ?
I found no hint in the docs...

would it make sense to use different names for the *.exe and *.com ?
(to not confuse them as i did ?)

Post by **psguru** » Mon Jan 07, 2008 7:53 pm

what is the difference between *.exe. and *.com ?

I found no hint in the docs...

would it make sense to use different names for the *.exe and *.com ?
(to not confuse them as i did ?)

Having both .exe and .com executables is a common trick to deploy a console front end for a GUI application. The same approach is used by Microsoft for their Visual Studio 6.0 (msdev.exe and msdev.com). See http://www.codeguru.com/cpp/w-d/console ... php/c3955/ for details.