Support Cygwin

[judah]

Currently the Windows/POSIX choice is an either/or choice at configure time. That doesn't make sense for systems with Cygwin.

The best would be to choose a RunTerm at runtime based on whether the program is being run under a POSIX terminal or the Win32 console. I'm not sure whether that's feasible.

[anonymous]

Depending on the configuration that's used, we should make sure that cabal install haskeline still works (on POSIX or Cygwin) even if a dependency like the terminfo Haskell library has not yet been installed.

[judah]

Bumping this ticket again...I'm not going to have access to a machine with Cygwin for at least another couple of weeks.

Also, it remains to be seen if the unix package can be compiled on Cygwin; see for example: http://www.haskell.org/pipermail/haskell-cafe/2008-September/047166.html

Without it, there's not much we can do here.

[judah]

At minimum, if we can't access POSIX commands on Cygwin then we should treat it as a file handle rather than trying to use Win32 commands.

[judah]

Replying to judah:

At minimum, if we can't access POSIX commands on Cygwin then we should treat it as a file handle rather than trying to use Win32 commands.

Upon further inspection that is exactly what occurs. However, the Cygwin X11 terminal behaves strangely: during a call to (e.g.) getLine, when the user presses an arrow key, the cursor moves!

I confirmed that C++ iostream-reading does the same thing, so the root cause is not necessarily a Haskell issue.

[judah]

See also #65