In this place specifically
https://bookdown.org/yihui/rmarkdown/markdown-document.html#markdown-variants

See rstudio/rmarkdown#2209

I don't know if this is better here or in your Cookbook.

I think it would be worth adding a short section documenting your own solution here to making RMarkdown appear in the Linguist Languages statistics of a GitHub repository by add the following line to the .gitattributes file

*.Rmd linguist-detectable

or even safer catch the fully lower case .rmd file extension as well

*.[Rr]md linguist-detectable

It would be worth explaining that by default Linguist ignores R Markdown (RMarkdown in Linguist) from the Languages statistics because it's defined as type: prose here and files of that type are excluded from the statistics without the linguist-detectable override as detailed here.

I assign the copyright of this contribution to the authors of the book "R Markdown: The Definitive Guide".

I recently bought the printed version of the book to support you, and its great!

I just read Section 2.2 Compile an R Markdown document. And I just got a little confused when reading:

"...With notebooks, you can run code chunks individually and see results right inside the RStudio editor. This is a convenient way to interact or experiment with code in an Rmd document, because you do not have to compile the whole document. Without using the notebooks, you can still partially execute code chunks, but the execution only occurs in the R console, and the notebook interface presents results of code chunks right beneath the chunks in the editor, which can be a great advantage..."

I turned to the online version of the book and discovered the same. As far as I can see in my Rmd files, I can indeed run code chunks and get the results right beneath the chunks in the editor, I'm sure this feature is something that has been added since that section was written.

So my suggestion is to update that section a little bit 😃.

https://bookdown.org/yihui/rmarkdown/notebook.html

At least small examples and links to where to look for more

---
output:
  html_document: default
---
```{scss}
$main-color: salmon;
.bright {
  background-color: $main-color;
}
```
This is a [*bright*]{.bright} word.

---
output:
  html_document: default
---
```{sass}
$main-color: salmon
.bright 
  background-color: $main-color;
```
This is a [*bright*]{.bright} word.

This section: https://bookdown.org/yihui/rmarkdown/powerpoint-presentation.html

Following the recent work that has been done: https://github.com/jgm/pandoc/pulls?q=is%3Apr+author%3Aundergroundquizscene+pptx

This will require a recent Pandoc version but it is possible the next version of RStudio IDE will ship it. We'll see.

cc @apreshill

Hi,
I'd like to adjust use the css customizations suggested in the section 4.1.5 on 'Adding a logo' to increase the logo size in all my slides, but I'm not sure which file I should edit. I only see the defaults.css file (under ...files>ioslides...>theme>css) that's created after I knit my current .Rmd presentation. Where can I add these customizations so that the bottom left logos in each slide appear a bit larger? And how can I make sure that this works robustly? Thanks!

rmdshower is available on CRAN now, so you may need to change the code

devtools::install_github("mangothecat/rmdshower")

in https://bookdown.org/yihui/rmarkdown/shower-presentations.html

Looking for detailed information on runtime:shiny_prerendered I just saw that the book does not explain this format of the rmarkdown 📦 . It is only mentioned in the Interactive Tutorial part, as something to use with learnr::tutorial.

I think this is a missing part of the rmarkdown 📦 in the reference Rmarkdown book. Something that should be added in another edition or in another book i.e advanced Rmarkdown.

This maybe a bother, I don't know? But I'm trying to follow the development of the book locally on my computer. Though I keep getting this error despite installing the missing packages:

Quitting from lines 635-893 (rmarkdown.Rmd)
Error: 'file_string' is not an exported object from 'namespace:xfun'
Execution halted
Error: Failed to compile the book to bookdown::pdf_book
In addition: Warning message:
running command '"C:/PROGRA1/R/R-341.4/bin/x64/Rscript" -e "bookdown::render_book('index.Rmd', 'bookdown::pdf_book', quiet = FALSE)"' had status 1
Execution halted
Error in render_book_script(output_format, envir, quiet) :
Error 1 attempting to render book
Calls: -> -> in_dir -> render_book_script
In addition: Warning message:
running command '"C:/PROGRA1/R/R-341.4/bin/x64/Rscript" _render.R "bookdown::pdf_book"' had status 1
Execution halted

Exited with status 1.

This is not an issue, but a recommendation.

I would like to suggest that in the docs available in the Rmarkdown book you include two examples in chapter 15 (parameterized reports):

• passing parameters as raw markdown text for the parameterized reports.
• setting the title using a parameter

This information is available in other parts of the book, but I think including them there would make easier for other people starting to create report templates.

For example, something as such in the .Rmd file:

---
output: html_document
params:
  author: author
  date: !r lubridate::today()
  set_title: title
  obs: my_text_chunk_with_markdown
title: "`r params$set_title`"  
---

This is my parameter with markdown in a chunk:

 ```{r, results='asis', echo=FALSE}
 cat(params$obs)
 ```

This is my parameter with markdown with code inline: `r paste(params$obs)`.

and something as such for the script that renders it:

rmarkdown::render(
  path_to_file,
  params = list(
                 set_title =  'title',
                 author =  'author',
                 obs = 'This is a text with *markdown* syntax.',
       ),
  output_file = 'my_report.html')
)

Nice book! Thanks for writing and publishing it. I'll grab a paper copy but likely refer to the electronic version more for easier searching.

In section "2.7.2 Shell Scripts", you suggest that Windows users can get the required functionality by installing Cygwin or WSL. I suggest that both require a bit more technical investment than is available and/or strictly necessary (not to mention large installations).

For the faint-of-heart (or space-limited), you can get most (admittedly) functionality out of Git for Windows, as it contains bash, awk/sed/tr, bzip2/bunzip2/unzip (but not zip!), git/diff/patch, grep/sort/uniq/wc, find/file/xargs, and many others. Two other alternatives (I have not tested them) are Gnu on Windows ("the lightweight alternative to Cygwin") and, in a pinch, even Rtools includes sh and a few of the above commands.

It's perhaps easier to push for GfW since RStudio already incorporates a bunch of git integration, so this would be a logical step (and a fluid endorsement of it in the book).

@yihui just a heads up that I renamed the branch from master to main here.

You need to reconfigure your local repo either using usethis::git_default_branch_rediscover() or git command

git branch -m master main
git fetch upstream
git branch -u origin/main main
git remote set-head origin -a

This a nice book! I noticed that it is an opensource book licensed under
Attribution-NonCommercial-ShareAlike 4.0 International. It means others can send pull requests to improve it, and the author( @yihui ) can earn money from it. I think it is a good practice of earning money from writing opensource books. I also want to write such a book.

It is no doubt that the author can commercially sell books under Attribution-NonCommercial-ShareAlike 4.0 if he or she writes the wholebook.

Say that I wrote an opensource book under Attribution-NonCommercial-ShareAlike 4.0 . I wonder whether I can sell my book after accepting others' pull requests? Can I use the pull request content commercially?

sigma.js v2 can render larger graphs using WebGL; wonder if it's under consideration to update 16.2 A widget example (sigma.js) to use sigma.js v2 .

See yihui/knitr#1987 and the new params chunk option

I assign the copyright of this contribution to the authors of the book "R Markdown: The Definitive Guide".

Just wondering, because some people would like to read the document in their native languages.

I think the three backticks on line 39 of:
https://github.com/rstudio/rmarkdown-book/blob/master/02-basics.Rmd
should not be there. The closing back backticks for the code block are already on line 36.

3.3.7.2 Keeping intermediate TeX
true does not work.
yes does

From what I can see, images are discussed briefly in Section 2.4.1 using the syntax [alt text or image title](path/to/image) . However, I feel the include_graphics() method is more stable, as is already explained in bookdown book.

I can't see any reference to this anywhere in the book, but wanted to ask where best to insert it before making a pull request? I would suggest that is shown quite early on, probably in the Basics chapter, but I cannot see a natural place for it to fit in currently.

Hi,大家好，
最近在学习R markdown，了解到这本正在写作中的书，下载了项目尝试build一下，有几个小问题反馈一下。
1、 01-intro.Rmd
1)、images/01-notebook-preview.jpg应改为images/01-notebook-preview.png，并重命名文件， png格式。

knitr::include_graphics("images/01-notebook-preview.png")

2、images/01-dynamic-document.jpg应改为images/01-dynamic-document.png，并重命名文件， png格式。

knitr::include_graphics("images/01-dynamic-document.png")

2、build HTML与word都可以，但build PDF出错，不知到写作团队测试过build PDF没有。我是菜鸟，还无法定位解决问题。不过知道PDF中laTeX数学公式等的效果比Word要方便很多和好很多。
···

sucess

bookdown::render_book('index.Rmd',"bookdown::word_document2")

Failed

bookdown::render_book('index.Rmd',"bookdown::pdf_book")
···
Error message:

Error in seq.default(dots[[1L]][[5L]], dots[[2L]][[5L]]) : 
  'to' must be a finite number
In addition: Warning messages:
1: `guides(<scale> = FALSE)` is deprecated. Please use `guides(<scale> = "none")` instead. 
2: In system2("python", c("-c", shQuote(code)), stdout = TRUE) :
  running command '"python" -c "print(1 + 1)"' had status 9009
3: In eval_asy() :
  System set-up not compatible with Asymptote, so chunks with asy engine will be skipped.
4: In eval_asy() :
  System set-up not compatible with Asymptote, so chunks with asy engine will be skipped.
5: In png::readPNG(path, native = TRUE, info = TRUE) :
  Image uses 16-bit channels but R native format only supports 8-bit, truncating LSB.
6: In knitr::write_bib(c(.packages(), "bookdown", "knitr", "rmarkdown",  :
  package(s) flextable, gt, gtsummary, formattable, reactable, rhandsontable, pixiedust, stargazer, tables, tangram, ztable, condformat, printr, styler, ezknitr, rmdformats, learnr, blogdown, spelling, blastula, workflowr, xaringanthemer, diagram, rmdrive, xaringanExtra, fusen not found
7: In utils::citation(..., lib.loc = lib.loc) :
  no date field in DESCRIPTION file of package 'datadrivencv'
8: In utils::citation(..., lib.loc = lib.loc) :
  could not determine year for 'datadrivencv' from package DESCRIPTION file
9: In utils::citation(..., lib.loc = lib.loc) :
 
 Error in seq.default(dots[[1L]][[5L]], dots[[2L]][[5L]]) : 
  'to' must be a finite number 

Thanks for the detailed super-helpful book, @yihui
Quick question. I read the sections on adjusting font-size in slides (R Markdown, ioslides presentation). Seems like I can use {.smaller} to change it for the whole slide.
I also read that footers can be added (if included in the file definition 4.2.3).

Qn: Is there a way to adjust the font size of individual lines in a particular slide? I tried appending the line with {.smaller} and {.bigger} but that doesn't work within the slide.
Thanks!

You may also suggest new topics to us. Thanks!

In chapter 3.2,

There is also a Restart R and Run All Chunks item in the Run menu on the editor toolbar, which gives you a fresh R session prior to running all the chunks.

It's now in the Session menu, not the Run menu😂

Should center include quotes?

fig.align: The alignment of plots. It can be 'left', center, or 'right'.

From rstudio/rmarkdown#2108 (comment)

we should add a part about Lua filters in this book based on the vignette: https://pkgs.rstudio.com/rmarkdown/articles/lua-filters.html

Intro and examples about Lua filters are in the Cookbook: https://bookdown.org/yihui/rmarkdown-cookbook/lua-filters.html

Trying your example file 04-valueboxes.Rmd my awesome icons are very small and at the left bottom corner of the box. Not sure if I missed something (some css styling?) or there is something wrong.

[The recommended change in css styles (e.g. W3schools or StackOverflow did not work for me (or I did not know where and how to apply them in the example code.]

If I wanted to create a new macro, similar to the $ or $$ macro for mathematics, how would I do that?

In that same line, if I wanted to create a parser that would take LATEX code in its native format and "translate" it so it could render as HTML without forcing the LATEX code to match the very limited Rmd syntax.

How do I underline in Rmd exactly? How do I embed nested HTML? It is very limited, so there needs to be some macro options such as "ignore". Include as HTML but ignore in terms of processing.

For example,

How can I include HTML blocks inline from an external source. Not in YAML as header/footer, but inline "similar to latex input syntax".

It seems like you are trying to build a templating language without all the necessary ingredients. If I want to hack on it, how do I do that?

https://github.com/rstudio/rmarkdown-book/runs/5249593990?check_suite_focus=true#step:10:29

@yihui do you know how to install this font on Linux ?

Seems like on CTAN there are some drop in replacement: https://ctan.org/topic/font

Seems like we don't use any specific one one bookdown and we use \usepackage{Alegreya} on R Markdown Cookbook

c796dfe#commitcomment-107718021

https://github.com/rstudio/rmarkdown-book/actions/runs/4622688973/jobs/8175668074#step:10:18

Probably something due to snapshoting HTML widgets not working

1. Clone repo.
2. make pdf.
3. Install a bunch of packages (list below).
4. Finally get this far with make pdf on the command line, but still no PDF.

~/rmarkdown-book + master$ make pdf
Rscript --quiet _render.R "bookdown::pdf_book" &&\
	mv _book/rmarkdown.pdf _book/rmarkdown-full.pdf
Error: Functions that produce HTML output found in document targeting latex output.
Please change the output type of this document to HTML. Alternatively, you can allow
HTML output in non-HTML formats by adding this option to the YAML front-matter of
your rmarkdown file:

  always_allow_html: yes

Note however that the HTML output will not be visible in non-HTML formats.

Execution halted
Error: Failed to compile the book to bookdown::pdf_book
Execution halted
make: *** [pdf] Error 1

Packages installed (in order, as error messages come up):

• revealjs
• bookdown
• blogdown
• rticles
• flexdashboard
• learnr
• pkgdown
• xaringan
• tufte

Ch 16 uses 'sigma' package, no such package present at CRAN, instead we have 'sigmajs'. Moreover book fails to compile under R 3.5.1. How to solve it, help plz.

Like navigation : https://community.rstudio.com/t/enable-navigation-symbols-in-beamer/128137/4

@yihui should I also apply the same deployment process as the other books for this one ?

Would that be ok ?

The bit.ly link in Section 15.4 is broken. It is supposed to point to a video about publishing parameterized reports.

Hello, I am trying to publish a report in Posit Connect. I've connected properly. I can render correctly. When publishing, execution halts, and this is the message:
{"code":109,"error":"This type of content is not allowed because it is prohibited by policy.","payload":null}
Error in POST():
! https://bookdown.org/__api__/applications/14123/deploy failed with
HTTP status 403
This type of content is not allowed because it is prohibited by policy.

I've looked at stack overflow, set to basic yaml configuration and always comes the same message. Any clue on how i can solve this?
Thanks in advance for reading me.

For rendering (in an intermediate dir) and publishing (e.g. to RStudio Connect).

Hello,
Manu thanks for your very interesting book.
I have a question concerning chapter "4.4 PowerPoint presentation" :
How can I get the page number be displayed on the generated slides ?
In advance many thanks
Best regards

Section 7.3.1 begins with

Every new slide is created under a horizontal rule (---).

In order to get a new slide, the dashes have to be followed by a new line. It took me a bit of googling to discover this. The text should be modified to describe actual behavior. For example add:

Note that the dashes have to be followed by a new line.

As blogdown is based on the bookdown package, would it make more sense to first have the chapter on bookdown before blogdown?