Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hard to tell when something went wrong #12

Open
kowey opened this issue Aug 21, 2012 · 2 comments
Open

hard to tell when something went wrong #12

kowey opened this issue Aug 21, 2012 · 2 comments

Comments

@kowey
Copy link
Contributor

kowey commented Aug 21, 2012

I'm not sure if it's always done this, but cabal-meta has taken to dumping the full block of stderr output at the end of a run. This can be useful, but in the current presentation (0.2.3.2?), it can make it hard to notice that an install failed (particularly if something goes wrong in the installation phase and not building). The exception is just buried.

@gregwebs
Copy link
Member

If you update the shelly dependency it should save output to a file instead of dumping it to a screen.

@kowey
Copy link
Contributor Author

kowey commented Aug 23, 2012

As with issue11, I think I might be on the latest shelly. I do note however that cabal-meta/shelly does seem to make the effort to print the error output again after the stderr stuff. I wonder how I missed that the first time. Hmm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants