-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
lessc writes error output to stdout #2457
Labels
Comments
ianthehenry
changed the title
lessc doesn't set an exit code
lessc writes error output to stdout
Feb 18, 2015
lukeapage
added a commit
that referenced
this issue
Feb 26, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When something goes wrong,
lessc
writes to stdout, not to stderrFor a simple repro, you can just invoke
lessc | wc -c
. Should be zero, as the error message should be written to stderr.(This issue originally included that
lessc
wasn't setting an erroneous exit code. It seems I was testing it wrong, andlessc
does do the right thing there. Not sure what I did...)Okay, edit 3: some errors don't correctly set an exit code. Here's one example:
But others do. An interesting roulette when using
lessc
from build scripts.The text was updated successfully, but these errors were encountered: