[Bug 17093] console not being connected to stdin/stdout correctly

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=17093

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> 2010-09-08 13:10:42 CDT ---
(In reply to comment #4)
> In wine-1.3.2-77-gec382f4, if I run:
> $ wine python.exe
> the '>>>' prompt shows up on the xterm, and I can interact with it there.
> If I run
> $ wine start python.exe
> the '>>>' prompt shows up in its own command.com window, and NOT on the xterm.
> I can interact with it there. The '>>>' shows up immediately, and does not
> require pressing return for it to appear.

 ok, then... actually... that's a bug! :)

> I'm not sure if it's fixed or not, based on your description.

 ... no, it isn't :)  the "fix" has resulted in "fixing" something that should
not have been "fixed".

 to get true bug-compatibility with win32, ironically you actually _need_ that
initial prompt to _not_ appear... but for the data to not end up coming out on
the xterm, either.

 but... mmmm... if you had to choose between one and the other, the present
situation is infinitely preferable, but strictly speaking it's still a bug (by
definition of "complete and total win32 interoperability") but just a different
one from the one originally reported :)

l.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.