JLine - Java console input library

There are some tweaks required when running under cygwin. See
http://jira.codehaus.org/browse/JRUBY-2675

Perhaps there's a change we could make in Jline to be smarter about this?

For a workaround to this problem, set system property "jline.terminal" to
"jline.UnsupportedTerminal" before calling ConsoleReader constructor. It
works for me in MiGW.

Method Terminal.setupTerminal contains a bug, where it compares system
property "os.name" with "windows". In Vista, os.name="Windows Vista", and
JLine wrongly assumes a UnixTerminal for ConsoleReader instances. I suggest
using a RegEx, like os_name.matches("^[Ww]indows.*), to check OS type.

Anyway, even after fixing this bug JLine does not work in Cygwin (nor
MinGW).

Here's a workaround (for Cygwin + xterm, JLine worked fine for me on Cygwin
+ bash):

#!/bin/bash
#
# Run Your App
#
stty -icanon min 1 -echo
java -Djline.terminal=jline.UnixTerminal jline.ConsoleRunner your.App "$@"
stty icanon echo

We have to use the UnixTerminal class because Cygwin + xterm is essentially
a Unix style terminal. The jline.UnixTerminal class attempts to execute
the commands "stty -icanon min 1" and "stty -echo" on start up and restores
the tty to its original setting on exit. However, probably because the
Windows version of the JDK knows nothing about Cygwin, these exec-ed
commands does not affect the current terminal. Executing these commands
outside the Java program helps to prep the tty for JLine interactive mode.

Without the two stty commands, JLine would still perform the commands
logically. But you won't see the full effect until you press the Enter
key. Works out OK if you close your eyes. :)