After upgrading dplyr to version 1.0.0 I’m a little bit annoyed by the warnings (actually you can’t suppress them with warnings = FALSE)

1

`summarise()` regrouping output by 'homeworld' (override with `.groups` argument)

But let’s look at an example:

When it comes to programming errors are a natural part of it. Sometimes you want to show such an error and then you want to show how to remove that error.

But if you have an error within your R-code chunk blogdown stops processing your article.

When you’re writing about RMarkdown using RMarkdown you may run into trouble when the RMarkdown parser parses the code you want to be simply embedded in your site.

I’ve started this blog five years ago using wordpress. But I admit that it was quite painful to write the articles about R in wordpress.

I had to write the R-code in RStudio, copy it to wordpress. Then I had to run the code and copy the output to wordpress, too.

Any time I want to make changes to the code this procedure gets quite tedious. I’ve also tried to do some steps at medium. But the steps for publishing were the same.

So I was pleased when I stumbled across blogdown. Using blogdown I can write my R code and the article in one step.

As I’m moving this blog from wordpress to blogdown (also see the book about blogdown) I was wonderung how I can get some nice syntax highlighting of the embedded R-code.

The first impression was quite sobering. I used the default .Rmd page type and I got not much highlighting. It was better than that I got at Medium with base functionality. But it’s not quite what I wanted.

But there are two other file types in blogdown.

.md is for simple markdown-pages without any R-code. But the other one .Rmarkdown seems to be more promising.