Thank you so much!

Sure, glad that helped.

Related: as of a8062f4, the default choice of interactive mode vs non-interactive mode is determined by isTRUE(getOption("knitr.in.progress")) instead of interactive(). That way, rmarkdown::render() in an interactive session aligns with expectations, and so does the built-in R Markdown functionality in the VSCode R extension. This is relevant here because errors, warnings, messages, and output are not relayed in interactive mode.

Hi there, it's me again. I think one of the more recent commits leads to an interesting question: target functions like tar_make and tar_visnetwork are evaluated in a fresh R session using callr, and this some how enables them to ignore knitr chunk options like message=FALSE and warning=FALSE. For example, when your have:

tar_visnetwork()

in a target markdown document we get:

with

tar_visnetwork(callr_function = NULL)

this message does not appear.

callr::r() supports arguments stdout and stderr which you can supply to the callr_arguments list in most targets functions.

Thanks! callr_arguments = list(show = FALSE) successfully hides the message.