References

This function calls bookdown::render_book().↩︎

Of course, no one can stop you from writing out some files in one chapter, and reading them in another chapter. It is hard to isolate these kinds of side-effects.↩︎

To include literal backticks, use more backticks outside, e.g., you can use two backticks to preserve one backtick inside: `` `code` ``.↩︎

Some examples are adapted from the Wikipedia page https://en.wikipedia.org/wiki/Characteristic_function_(probability_theory)↩︎

You may consider using the code chunk labels.↩︎

Do not forget the leading backslash! And also note the parentheses () after ref; they are not curly braces {}.↩︎

The type name is case-insensitive, so it does not matter if it is manual, Manual, or MANUAL.↩︎

An iframe is basically a box on one web page to embed another web page.↩︎

To see more details on how an identifier is automatically generated, see the auto_identifiers extension in Pandoc’s documentation http://pandoc.org/MANUAL.html#header-identifiers↩︎

The backslash before : is due to a technical issue: we want to prevent Pandoc from translating the link to HTML code <a href="..."></a>. More details at https://github.com/jgm/pandoc/issues/2139.↩︎

For the bs4_book() format, the edit, history, and view fields have no effect and similar configuration can be specified with the repo argument of the output function.↩︎

This directory has to be an RStudio project.↩︎

You need to authorize the Travis CI service for your repository on GitHub first. See https://docs.travis-ci.com/user/getting-started/ for how to get started with Travis CI.↩︎

Follow the indenting rule if the literal code chunk is to be displayed in other environments such as a list: https://pandoc.org/MANUAL.html#block-content-in-list-items↩︎