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 (0)
No replies.