Fix perltidy error output #229
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tsilvap
force-pushed
the
fix-perltidy-error-output
branch
from
3623c70 to
21002aa
Compare
tsilvap
force-pushed
the
fix-perltidy-error-output
branch
from
21002aa to
2e02fc6
Compare
By default, perltidy writes errors to a file called `perltidy.ERR`. To make it write to stderr (which is what is assumed by format-all), we need to pass a "--standard-error-output" flag.
|
I was doing some local rebasing in magit and ended up force-pushing to this branch somehow? Welp, sorry about this, should be fixed now. |
|
No problem. Good catch. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, perltidy writes errors to a file called
perltidy.ERR. To make it write to stderr (which is what is assumed by format-all), we need to pass a "--standard-error-output" flag.