With render(), message=FALSE does not print to console as expected about rmarkdown

[atusy]

Hi. This sounds like knitr's issue.

Anyway, it sounds good to me to logging on the console or somewhere.
In this way, users can stop knitting once they find some unexpected messages or warnings.

On the other hand, I would keep the current behavior of the chunk options (message, warning and error) for the simplicity.
An alternative approach would be to provide package options for logging, e.g., knitr::opts_knit(loglevel = "warning", logfile = "stderr").

According to the docs

Would you provide a link to the doc that describes your expected behavior?
I briefly read through https://yihui.org/knitr/options/ , but cannot find it.

[bbimber]

Thanks for the fast reply. It is possible knitr and not rmarkdown. Should anyone else run into a need to log to the console, I just found the logger package:

logger::log_info('I will print to the console!')

Which is a much more direct way to address this.

[yihui]

FALSE will completely suppress the messages. If you want messages to be printed to the console, you can use NA. More info here: https://yihui.org/en/2022/12/message-false/ (I need to update the doc at https://yihui.org/knitr/options/).

[bbimber]

@yihui Thank you, your first post fits. I was sure the behavior used to be that message=FALSE would print them, but I could not find the docs on it. message=NA does behave as you posted. Nonetheless, I think explicitly logging is probably a more clear route and I think we'll use this.

It would be great if you could update the docs since it took a while to figure out the expected behavior.

[yihui]

I'll update the docs for sure. Sorry about the confusion!

[yihui]

Docs have been updated. Thanks!