Chunk Reference/Macro

Sweave has the feature of chunk reference to reuse chunks with the syntax <<chunk-label>> (without = compared to <<>>=), e.g.

<<chunk1>>=
1 + 1
@

<<chunk2>>=
<<chunk1>>
@

In chunk2, the code in chunk1 will be inserted. This feature is also available in knitr, but note knitr supports arbitrary (finite) levels of recursion in chunk references (Sweave only supports one level), i.e. one chunk can reference another chunk which references yet another chunk.

This feature can be turned off via the chunk option ref.chunk = FALSE, and then the <<>> markers will not be touched.

This same <<chunk-label>> syntax will work in markdown, to reuse a previous named markdown chunk within another chunk, even though your .Rmd editor will likely flag the line as an unexpected token.

There are still other approaches to reuse chunks in knitr.

1. use the same label as the previous chunk to be reused
2. use the chunk option ref.label to reference another chunk

Use the same label

An example for the first approach:

<<chunk1, echo=TRUE, results='hide'>>=
1 + 1
@

<<chunk1, echo=FALSE, results='markup'>>=
@

The second chunk is empty, so knitr will look for another chunk with the same label but is not empty, and use the code from that chunk. The key is to leave a chunk empty to use code from other chunks. One problem with this approach is that you cannot cache both chunks since their MD5 digests are different, and knitr only allows one set of cache files per label.

Use chunk option ref.label

An example for the second approach:

<<chunk1, echo=TRUE, results='hide'>>=
1 + 1
@

<<chunk2, ref.label='chunk1', echo=FALSE, results='markup'>>=
@

The second chunk uses a different label, so cache is no longer a problem. Obviously the second approach is a more general solution.

This feature enables us to separate R code and R output in the output document. For instance, we can use echo=FALSE in the body of an article to hide R code, and use chunk references in the appendix to show R code (with eval=FALSE, ref.label=...).

Donate

As a freelancer (currently working as a contractor) and a dad of three kids, I truly appreciate your donation to support my writing and open-source software development! Your contribution helps me cope with financial uncertainty better, so I can spend more time on producing high-quality content and software. You can make a donation through methods below.

• Venmo: @yihui_xie, or Zelle: xie@yihui.name

• Paypal

  • If you have a Paypal account, you can follow the link https://paypal.me/YihuiXie or find me on Paypal via my email xie@yihui.name. Please choose the payment type as “Family and Friends” (instead of “Goods and Services”) to avoid extra fees.

  • If you don’t have Paypal, you may donate through this link via your debit or credit card. Paypal will charge a fee on my side.

• Other ways:

  WeChat Pay (微信支付：谢益辉)	Alipay (支付宝：谢益辉)

When sending money, please be sure to add a note “gift” or “donation” if possible, so it won’t be treated as my taxable income but a genuine gift. Needless to say, donation is completely voluntary and I appreciate any amount you can give.

Please feel free to email me if you prefer a different way to give. Thank you very much!

I’ll give back a significant portion of the donations to the open-source community and charities. For the record, I received about $30,000 in total (before tax) in 2024-25, and gave back about $15,000 (after tax).