Hadley Wickham

@cderv would you mind working with the IDE/quarto teams to figure where's the best place to expose this info?

A small but useful feature is using `is_interactive()` instead of `interactive()`, and having some way to control what happens when run in a non-interactive environment.

This is what I've come up with: ```R cli_menu

Probably want some kind of helper like `cli_readline_simulate()` that you could use inside (e.g.) a snapshot test. It'd just need to be a thin wrapper around `withr::local_options()`.

@gaborcsardi thanks; that was a remnant of an older approach.

It looks like `deprecate_warn0()` gets called twice, the second time with call stack ``` ▆ 1. └─rmarkdown::render("vignettes/test.Rmd") 2. └─knitr::knit(knit_input, knit_output, envir = envir, quiet = quiet) 3. └─knitr:::process_file(text, output) 4....

I now realise this error is coming from `layer_smooths()` - we need a better error message here. Maybe list available vars?

@eriksquires could you please provide a simple reprex illustrating the problem?

@eriksquires thanks! That's really is terrible performance 😞

I'd say we should fix this by automatically recycling the parameters to the correct length (or giving up with an error) in R.