GitLab

As noted by GHC #20085, the ccall calling convention does not support
variadic functions.

This will avoid future breakage

See https://downloads.haskell.org/ghc/8.10.3/docs/html/users_guide/using-warnings.html?highlight=wcompat#ghc-flag--Wcompat-unqualified-imports

Win32 provides a few console primitives as of the 2.9 release, resulting
in name shadowing warnings with our own local versions. Hide those from
Win32 to avoid the warnings.

* Use gsWidth to calculate the width of completions

* Update variable names and comments to mention "width", not "length"

Allow base-4.15

See GHC Proposal 287:
https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0287-simplify-subsumption.rst

Also bump base upper bound.

See GHC Proposal 287:
https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0287-simplify-subsumption.rst

See GHC Proposal 287:
https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0287-simplify-subsumption.rst

GHC's build currently can't handle packages with both a library and
a binary.  Help out by allowing a build to disable the executable,
which is only needed for the test.  (So disable the test as well.)

Also bump the version to 0.8.0.1.

* Fix wcwidth to handle non-BMP characters on Windows

* Encode String into UTF-16 when writing to Windows console

* Decode UTF-16 when processing input from Windows console

There are also a couple of other monads that could plausibly have this
instance, but since none of them seem to be exported I left them alone.

Also test ghc-8.6.3 in Travis CI instead of 8.6.1.

Make it a looped KeyCommand inside a single call to runInputCmdT,
rather than calling runInputCmdT once for each character.

This removes some noise by letting us clear the prompt before printing the key that was read. 
 It also hopefully makes it closer to "real" results when entering multiple keys (e.g., holding them down).

This works with `stack` and `cabal new-test`.  The latter
uses the `build-tool-depends` field to locate the binary.

Also:
- Remove the reference to the nonexistent main file on Windows.
- Make the test binary return a nonzero exit code when it fails.

Still TODO: test in CI.

This change is motivated to make it easier to run the unit tests:

defined two executable targets in the cabal file
added run_unit_tests.sh script
one test is failing independent of the changes:

```
Failure in: 0:interaction:2:tab completion:0
tests/RunTTY.hs:106
expected: ["dummy-\206\188\206\177\207\131/\r\nbar \207\130\206\181\207\129\207\132\r\n0:dummy-\206\188\206\177\207\131/"]
but got: ["dummy-\206\188\a\a"]
```

Fixes #74 as well enough as Haskeline currently can.  It returns
a `Bool` rather than `Maybe Key` since Haskeline doesn't expose its
`Key` type.  But this should be enough for the "press any key to continue"
functionality described in the feature request.

Fixes #72.

Fixes #87.

Similar to `KillLine`, add two new "keys" `ReverseSearchHistory` and `ForwardSearchHistory` which bind to the incremental history search functionality.

Original patch by @boris-stepanov (#90).

Fixes #3.