Am 23.04.2011 00:30, schrieb Dan Stromberg:
> On Thu, Apr 21, 2011 at 1:42 PM, David Eisner <deisner@...
> <mailto:deisner@...>> wrote:
> On Thu, Apr 21, 2011 at 4:33 PM, Philip Jenvey
> <pjenvey@... <mailto:pjenvey@...>> wrote:
> > It probably hasn't actually hanged, it may just be that the prompt
> isn't showing up (because interactive mode wasn't detected correctly).
> > Try running the jython script (for unix platforms) instead of
> jython.bat, it should have a workaround for this issue. Maybe the
> .bat file should too but I'm not sure about that.
> Actually, I am running the jython bash script in cygwin (see previous
> message). I'm only running jython.bat in a Windows cmd shell, where
> everything works. But you're absolutely correct: it isn't hanging,
> it's just not showing the prompt, or my input. If I type '1+1<enter>'
> and '7*7<enter>', I see Jython's output, but nothing else:
> $ head -3 `which jython`
> #!/usr/bin/env bash
> # This file was generated by the Jython installer
> $ jython
> So now the question is, why isn't it echoing the prompt, or my input?
> Some Windows applications do console I/O by writing to video RAM
> directly, instead of *ix's more disciplined approach - which some
> Windows applications use instead.
> Presumably, Jython is one of those that writes directly to video RAM.
> For these, you're pretty much stuck with cmd.exe or similar.
And why did it work before the release of jython2.5.1?
Doing some things a bit different does not mean, there is no solution
for it, and there was once a solution that was cancelled by thinking,
this old beviour is non standard let us drop it. That cygwin users are
annoyed about this obvious wrong solution did not matter.