Changes ======= Version 0.8.0.4 --------------- * On Windows, `hSupportsANSI` now recognises if the handle is connected to a 'mintty' terminal. Version 0.8.0.3 --------------- * On Windows, try to enable ANSI on ConHost terminals even if a TERM environment variable exits (such as with the Hyper 2 terminal) * Minor improvements to Haddock documentation Version 0.8.0.2 --------------- * Improve README and Haddock documentation * On Windows, fix compatability with earlier GHC versions * Drop support for GHC versions before 6.12.1 (released December 2009) Version 0.8.0.1 --------------- * On Windows, if the standard output channel is valid but not a ConHost terminal, assume it is ANSI-enabled rather than failing * On Windows, output the improved error message to the standard error channel rather than the standard output channel Version 0.8 ----------- * Make the fields of `SGR` strict * Make compatible with GHC 8.2.2 * Improve the error message on Windows when not ANSI-capable or ConHost * Recognise Appveyor build environment as ANSI-enabled Version 0.7.1.1 --------------- `getReportedCursorPosition`: don't let the cursor reporting code be echo'd Version 0.7.1 ------------- * Allow saving, restoring, and querying the current cursor position * Fix a couple of issues with the Reset emulation on Windows Version 0.7 ----------- Add 24-bit RGB color support Version 0.6.3.1 --------------- Fix Windows + ghc 7.8 compatibility Version 0.6.3 ------------- * Add ANSI support for Windows * Add compatibility with Win32-2.5.0.0 and above Version 0.6.2.3 --------------- Add an example to the haddocks Version 0.6.2.2 --------------- Fix a GHC 7.10 warning Version 0.6.2.1 --------------- Restore compatibility with GHC 7.4 and older Version 0.6.2 ------------- * Add `hSupportsANSI` * Drop support for `base < 4` Version 0.6.1.1 --------------- Fix to build with GHC 7.8 on Windows Version 0.6.1 ------------- * `BoldIntensity` no longer changes background color on Windows * `setSGR []` was not equivalent to `setSGR [Reset]` on Windows, even though it should be according to the documentation. This is now fixed.