2026-08-08 12:41 UTC
So the weird wilcox.test() behavior I saw yesterday happened because I'd unwittingly set the session to suppress all warning messages -- not just in my output, which had been my intention, but to the console. Is there a better way to handle warnings when knitting a report, such that functions that issue them frequently for ignorable things don't litter a report, but working inside a session in the console, I'll still see everything I need to see? #rstats
Replies (1)
-
@nxskok@cupoftea.social 2026-08-08 14:55
@emjonaitis@mathstodon.xyz wouldn't putting a warnings: false in the yaml at the top of the document do this? When you explicitly knit the document, you won't see them, but while you are running things chunk by chunk you well.