[GH-ISSUE #1563] Use stderr for errors and stdout for normal output #2555

New issue

Closed

opened 2026-03-07 20:08:51 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:08:51 +03:00

Owner

Originally created by @gtirloni on GitHub (Apr 12, 2025).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1563

stderr is being used for normal output when the tool is not exhibiting any errors.

It might be reporting warnings from the rules, but that's its normal mode of operation.

Instead, please consider using stdout for everything except errors/warnings that disrupt the tool's operation, not for errors/warnings in the content that it's evaluating.

Originally created by @gtirloni on GitHub (Apr 12, 2025). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1563 `stderr` is being used for normal output when the tool is not exhibiting any errors. It might be reporting warnings from the rules, but that's its normal mode of operation. Instead, please consider using `stdout` for everything except errors/warnings that disrupt the tool's operation, not for errors/warnings in the content that it's evaluating.

kerem

2026-03-07 20:08:51 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-07 20:08:52 +03:00

Author

Owner

@DavidAnson commented on GitHub (Apr 12, 2025):

This library doesn't output anything to console. If you are using one of the associated CLI tools, you'll need to identify which one and should open an issue in their repository. It would also be helpful to say what specific output you think is not appropriate for stderr.

@DavidAnson commented on GitHub (Apr 12, 2025): This library doesn't output anything to console. If you are using one of the associated CLI tools, you'll need to identify which one and should open an issue in their repository. It would also be helpful to say what specific output you think is not appropriate for stderr.

kerem commented

2026-03-07 20:08:52 +03:00

Author

Owner

@gtirloni commented on GitHub (Apr 12, 2025):

You're right, I created the issue in the wrong repo. I'm using markdownlint-cli. It outputs everything to stderr (rules that are violated lille which file and line). Sorry for the noise.

@gtirloni commented on GitHub (Apr 12, 2025): You're right, I created the issue in the wrong repo. I'm using markdownlint-cli. It outputs everything to stderr (rules that are violated lille which file and line). Sorry for the noise.