limiting size of data tables rendered when the markdown is knitted

What is the most practical manner to include all steps utilized within the rmarkdown knitted document? Id love to save all the steps (including reviewing the entire dt) as it assists me with my learning review, but those steps also produce huge output sections within the rmarkdown document that greatly slow the knit process........any hints from vets?

To limit output while still seeing how it was produced

'{r, echo=TRUE} mtcars*2.5 |> head(x = _,4) '
but if you also want to review the entire dt, where will it be visible. In general, code in the IDE and present, reproucibly, in rmarkdown, which will allow each tool to do what it's designed for.

1 Like

thanks, thats kinda what I though........means Im spending too much time in the rmd...

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.