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

Tidy output going to stderr #763

Closed
phonedog365 opened this issue Oct 22, 2018 · 2 comments
Closed

Tidy output going to stderr #763

phonedog365 opened this issue Oct 22, 2018 · 2 comments

Comments

@phonedog365
Copy link

HTML Tidy for Apple macOS version 5.6.0 installed via Brew and updated. Output is going to stderr. Ran command tidy -e [file] | more and notice output was bypassing more. Ran hilite tidy -e [file] and it verified all output was going to stderr. Man page indicates:

--output-file String This option specifies the output file Tidy uses for markup. Normally markup is written to stdout.

Thanks!

@geoffmcl
Copy link
Contributor

@phonedog365 maybe I completely misunderstand the problem... sorry...

If you use -e, or -errors, or --markup no on the command line, or add markup: no to a config file, then there should be no stdout, that is no pretty printed html output, thus nothing would be passed to | more...

So given say tidy -e in_file.html[ | more], with or without the | more, the only output should be warnings, errors, and info, all sent to stderr, as documented...

What is the problem you see?

Please clarify... thanks...

@phonedog365
Copy link
Author

I just now read this (as if for the first time!):

If no input file is specified, Tidy reads the standard input. If no output file is specified, Tidy writes the tidied markup to the standard output. If no error file is specified, Tidy writes messages to the standard error.

I would have (wrongly?) assumed that any error (stderr) output from Tidy would be a program error and not output matching errors found with the source file. To me that seems... wrong. But I'm not a committer and I truly appreciate your efforts in maintaining the software. Thanks!

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

No branches or pull requests

2 participants