| --- | |
| title: "Get verbatim R chunks in R Markdown" | |
| author: "Jenny Bryan" | |
| date: "18 September, 2014" | |
| output: | |
| html_document: | |
| keep_md: TRUE | |
| --- | |
| My periodic revisitation of "how can I include a verbatim R chunk in `.rmd`"? This time I am writing it down! Various proposed solutions: |
| Write a program that does what it’s supposed to do | |
| Write idiomatic code | |
| Debug a program that you wrote | |
| Debug a program someone else wrote | |
| Debug the interaction between a system you wrote and one you didn’t | |
| File a good bug report | |
| Modify a program you didn’t write | |
| Test a program you wrote | |
| Test a program you didn’t write | |
| Learn a new programming language |
There's a more compelling illustration here: https://github.com/mdsumner/dputtruncat/blob/master/README.md
roms_names <- c("xi_rho", "eta_rho", "s_rho", "ocean_time", "s_w", "xi_u",
"eta_u", "xi_v", "eta_v", "tracer", "boundary", "xi_psi", "eta_psi")
axes_summary <- structure(c(1443L, 392L, 31L, 31L, 32L, 1442L, 392L, 1443L, 391L,
2L, 4L, 1442L, 391L), .Names = roms_names)
dput(axes_summary)
by Tatiana Mac
Last updated 14 April 2021
As speaking comes with immense privilege, I have crafted a speaker rider to set expectations and boundaries around my engagement. I am grateful to all the conference organisers who have brilliantly hosted me. I would love to continue to exercise this privilege to speak at conferences, and use this privilege to make the landscape more accessible and beneficial to tech's most historically excluded and marginalised communities.
😫 I provide a lot of explanations for those of you who never had to consider these things. Most thoughtful conferences I've attended check most of these boxes intrinsically, particularly when conference runners are experienced speakers. They get it.