How to specify tidy options?

[Ifitrains]

From this question, I was wondering how to use tidy options in the new chunk options, I thought something along these lines could work, but it does not:

---
format: revealjs
---

## A title


Here is some example code


```{r}
#| eval: false
#| echo: true
#| tidy: true
#| tidy-opts: 
#|   - width-cutoff=60
multipoint <- sf::st_multipoint(rbind(c(3.2,4), c(3,4.6), c(3.8,4.4), c(3.5,3.8), c(3.4,3.6), c(3.9,4.5)))

[mcanouil]

There is no "=" in YAML, it's ":".

To define it in code cell:

```{r}
#| eval: false
#| echo: true
#| tidy: true
#| tidy.opts: 
#|   - width.cutoff: 60
```

Or

```{r}
#| eval: false
#| echo: true
#| tidy: true
#| tidy.opts: { width.cutoff: 60 }
```

If the option with the "dash" notation does not work (it should I think), try with the "dot".

To define it globally, see https://quarto.org/docs/computations/r.html#knitr-options.

[mcanouil]

@cscheid I think there is something fishy here. tidy-opts is listed in reference docs, is listed in the options to be normalised, i.e., it's converted to tidy.opts, but somehow there is something getting in the way leading to an error.
I can take a deeper look into this.

In some aspects, it's related to #5744 and other issues regarding "dash" versus "dot" notations.
There is, in my opinion room, for enhancement to reduce cognitive hassle between the two notations.

@cderv in the eventuality you already have some insights 😏

[cderv]

I believe this is the hint of an issue in our normalization process and how options are (or rather should be) replaced.

1. knitr defines tidy.opts = NULL by default
2. Setting tidy-opts will be parsed by knitr as tidy-opts and will not replace the default one registered at tidy.opts
3. Normalization is done by Quarto as an option hooks. This means options are process and tidy-opts is indeed changed to tidy.opts.
4. But not options in knitr have twice tidy.opts and only the first one will apply (tidy.opts = NULL).

So our normalization is buggy ! Doing tidy.opts directly in a chunk will not have the issue because at the end knitr parses the options anyway.

So

• we need to fix the normalization process to replace options in Quarto
• We probably need to make knitr do the normalization itself at some point when parsing the YAML chunk options

[mcanouil]

IMHO, with the YAML style in knitr, It would make sense to me, that knitr natively supports "dash" notations itself.

[cderv]

Issue opened to track this : #5852

thanks everyone ! We would not have found this easily !

[mcanouil]

Closing this in favour of the issue.

[cderv]

FWIW from next knitr version 1.44 (and from current dev version 1.43.7), all dash options are changed to their dot versions. This includes tidy-opts which means it can be used in YAML and correctly replace knitr's defaults