You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmmm, you might need to tweak something in your test suite runner (ghciwatch captures output so it might be seeing that stderr is not a tty or whatever), or this might be a more fixable bug with ANSI escape handling...
I was going to open an issue myself for another problem with colors -- maybe related?
If I run https://github.com/chreekat/cubectl , the main function prints a bunch of lo-tech tests. One of them is pretty-printing that involves a bunch of color.
In the screenshot below, there are two tmux panes.
In the upper one is the output of running main from cabal repl.
The lower pane has the output of ghciwatch --command "cabal repl ." --watch . --error-file errors.err --clear --test-ghci main
Since the color blocks are just a space character with colored background, nothing shows up at all in ghciwatch.
What happened?
When running a test suite (hspec) with
ghciwatch
with the following command:Colors to not appear in the test output.
In addition to passing in
-fdiagnostics-color=always
thru a cli option, I have added it toghc-options
inmy-app.cabal
andproject.cabal
:What did you expect to happen?
I expected the colored output from the test to be visible in
ghciwatch
. Here's a screenshot of the output:Here's what I would expect the it to look like (via ghcid):
Steps to reproduce the issue
I think there's enough info above!
The version of ghciwatch with the bug
ghciwatch 1.0.1
The text was updated successfully, but these errors were encountered: