1. 31 May, 2020 1 commit
  2. 27 May, 2020 1 commit
  3. 26 May, 2020 1 commit
  4. 25 May, 2020 1 commit
  5. 12 Feb, 2020 1 commit
  6. 08 Feb, 2020 3 commits
  7. 07 Feb, 2020 1 commit
  8. 03 Jan, 2020 2 commits
  9. 29 Dec, 2019 2 commits
  10. 12 Nov, 2019 1 commit
  11. 27 May, 2019 1 commit
  12. 10 Feb, 2019 1 commit
  13. 28 Jan, 2019 1 commit
    • Judah Jacobson's avatar
      Turn debugTerminalKeys into a single loop. (#111) · 0b4f698d
      Judah Jacobson authored
      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).
      0b4f698d
  14. 24 Jan, 2019 1 commit
    • Judah Jacobson's avatar
      Convert the test to a test-suite. (#110) · 3214a170
      Judah Jacobson authored
      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.
      3214a170
  15. 23 Jan, 2019 1 commit
    • Kamil's avatar
      Define executable targets in the cabal file for tests (#103) · 4e7e0424
      Kamil authored
      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"]
      ```
      4e7e0424
  16. 22 Jan, 2019 1 commit
    • Judah Jacobson's avatar
      Add the new function `waitForAnyKey`. (#108) · 6b145aac
      Judah Jacobson authored
      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.
      6b145aac
  17. 21 Jan, 2019 4 commits
  18. 17 Jan, 2019 1 commit
  19. 10 Dec, 2018 1 commit
  20. 20 Oct, 2018 2 commits
  21. 06 Oct, 2018 5 commits
  22. 24 Jun, 2018 2 commits
  23. 20 Jun, 2018 1 commit
  24. 18 Jun, 2018 1 commit
  25. 03 Jun, 2018 1 commit
  26. 02 Jun, 2018 1 commit
  27. 16 Apr, 2018 1 commit