With a new release of the evaluate package (v0.19) last week, the meanings of the chunk option message = FALSE and warning = FALSE in knitr have changed. Previously, they meant that messages and warnings would not be captured at all. Normally the messages would be sent to the console.

That was both confusing and inconvenient. When users set message = FALSE, the more likely intention is “I’m sure I don’t want to see any messages anywhere from this code chunk”, instead of “I don’t …