You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second chunk (B) isn't rendered in the output. It seems to be caused by starting the chunk with a <<>> because putting something in front of it solves the issue (C).
The text was updated successfully, but these errors were encountered:
Hi @snhansen! It turns out this is actually a bug in knitr. I commented on a relevant issue that independently discovered the same behavior. In your case, the trick you can apply is to make sure that the <<x>> elements aren't ever the first thing on a line:
With knitr >= 1.48.3 we'll be able to set ref.chunk = FALSE for epoxy_latex chunks. (See linked issue above for details.) I'll work on adding this epoxy soon.
Great! I just tried the example in the OP with knitr 1.48.3 and the issue has been resolved without setting ref.chunk = FALSE for the chunks. So it seems that minimal fix that was initially committed did the job in this particular case.
Consider this Quarto markdown document:
The second chunk (B) isn't rendered in the output. It seems to be caused by starting the chunk with a
<<>>
because putting something in front of it solves the issue (C).The text was updated successfully, but these errors were encountered: