{
  "title": "Trying to continue the streak in 2018 from last year (https://t.co/Bc5Lg7xql3)... The R Markdown book just arrived (thanks, everyone: https://t.co/bSXP1sxESf) Wait, it is still July? Okay, I'm going to sleep through the rest of this year. https://t.co/DeZBiqpDEx",
  "date": "2018-07-21"
}

# blogdown

> **Sam Langton** (@sh_langton; 17/3): More tessellated map tests in R using IMD data for Birmingham. No easy solution to get a visually appealing and geographically accurate map... depends on the aim. Massive difference in processing time. There's my first #blogdown post in here somewhere #rstats #sf #geogrid https://t.co/GWMtVh2qXj  [&#8618;](https://twitter.com/xieyihui/status/1020215903823310849)

<!-- -->


> **James Waters** (@lovetheants; 13/5): After four years, updated my lab's website using #Rstats and #blogdown. https://t.co/l7Y8bsCIEO https://t.co/G2vJiBJhAW  [&#8618;](https://twitter.com/xieyihui/status/1020207296444616706)

<!-- -->


> **Charles T. Gray** (@cantabile; 6/0): @xieyihui @fellgernon @apreshill @bikesRdata @katrinafee Post is up! So much prettier than on github. Thanks for the awesomeness of blogdown, @xieyihui @apreshill 
>
https://t.co/qQXRUYOHoZ  [&#8618;](https://twitter.com/xieyihui/status/1020150549696729089)

<!-- -->


> **Yihui Xie** (@xieyihui; 2/1): @recleev @hivickylai Actually I don't like that solution. My personal favorite solution is https://t.co/nYsSzVR2ar It was briefly explained in the blogdown book: https://t.co/i1T1hvElR1  [&#8618;](https://twitter.com/xieyihui/status/1020142028020224000)

<!-- -->


> **Recle Etino Vibal** (@recleev; 2/0): @xieyihui @hivickylai Thanks @xieyihui I tried your favorite and it works. I mainly browsed over sections with js and html in #blogdown book because I really don't understand js or html 😂🤣😭 Thanks for #blogdown I don't need to worry much about js or html except for a few cases like this 😊  [&#8618;](https://twitter.com/xieyihui/status/1020153223926071297)

<!-- -->


> **Yihui Xie** (@xieyihui; 2/0): @fellgernon @cantabile @apreshill @bikesRdata @katrinafee Not relevant to blogdown version, I guess. Why did you clean up the .html files? https://t.co/6NCmDV60Ag These files are actually necessary (and shouldn't be ignored in .gitignore).  [&#8618;](https://twitter.com/xieyihui/status/1020140040222138368)

<!-- -->


> **Jacquie Tran** (@jacquietran; 0/1): Blogdown #rstats folks: Has anyone had problems with .md files rendering properly to HTML? My 'About' page used to show up as expected (last time I checked, months ago), but not now... https://t.co/aG6EDSpGBy  [&#8618;](https://twitter.com/xieyihui/status/1020269096410071040)

<!-- -->


> **Recle Etino Vibal** (@recleev; 0/1): If you invested 6k every six months since 1987 Jun in @PhStockExchange index, you would have been a millionaire by 2018 Jun #stocks #investment created with #rstats #blogdown @GoHugoIO @MathJax @hivickylai #introduction https://t.co/eCGCrjinHt  [&#8618;](https://twitter.com/xieyihui/status/1020250529992126464)

<!-- -->


> **Jacquie Tran** (@jacquietran; 0/0): So I 'addressed' my #blogdown problem without solving it. Ye olde About page is now in draft mode. I want static pages on my blog eventually, but late on a Friday night is not the time to solve this problem...  [&#8618;](https://twitter.com/xieyihui/status/1020278271974375426)

<!-- -->


> **Jacquie Tran** (@jacquietran; 0/0): FYI I've tried updating R and all installed packages, including blogdown. The .md file seems to render as expected when I serve site locally, but somehow not when I push changes to the repo and try to view my site online?  [&#8618;](https://twitter.com/xieyihui/status/1020270794838978560)

<!-- -->


> **Jacquie Tran** (@jacquietran; 0/0): I have a subfolder 'about' in the 'content' directory, with an 'https://t.co/xAZp27uuUa' file, following the structure specified in the blogdown book.
>
My blogdown repo is here for those that might be willing and able to help me: https://t.co/vBaPNso68x  [&#8618;](https://twitter.com/xieyihui/status/1020269849660948480)

<!-- -->


> **stevenmosher** (@stevenmosher; 0/0): @pgbovine Blogdown post  [&#8618;](https://twitter.com/xieyihui/status/1020274782862917632)

<!-- -->


> **Recle Etino Vibal** (@recleev; 0/0): #RLessonOfTheDay @xieyihui prefers this solution to @MathJax in @GoHugoIO #blogdown https://t.co/KSkMPwo5fG  [&#8618;](https://twitter.com/xieyihui/status/1020187230105550848)

<!-- -->


# bookdown

> **Yihui Xie** (@xieyihui; 181/40): Trying to continue the streak in 2018 from last year (https://t.co/Bc5Lg7xql3)... The R Markdown book just arrived (thanks, everyone: https://t.co/bSXP1sxESf) Wait, it is still July? Okay, I'm going to sleep through the rest of this year. https://t.co/DeZBiqpDEx  [&#8618;](https://twitter.com/xieyihui/status/1020408050421780480)

<!-- -->


> **Amber Thomas** (@ProQuesAsker; 28/4): I think I recommend RMarkdown to anyone who will care to listen. @xieyihui, J.J. Allaire, and @StatGarrett's new book gets into the nitty gritty Rmd magic✨ that I didn't even know about! Reports, presentations, interactive tutorials, websites and more!👇📖https://t.co/YLDpve11Oi  [&#8618;](https://twitter.com/xieyihui/status/1020427257108545536)

<!-- -->


> **Yihui Xie** (@xieyihui; 2/1): @recleev @hivickylai Actually I don't like that solution. My personal favorite solution is https://t.co/nYsSzVR2ar It was briefly explained in the blogdown book: https://t.co/i1T1hvElR1  [&#8618;](https://twitter.com/xieyihui/status/1020142028020224000)

<!-- -->


> **Karl Blumenthal** (@landlibrarian; 2/0): I'm over the moon for this bookdown site 🌛 An accessible OER model to follow: https://t.co/CPbWhSNwYs  [&#8618;](https://twitter.com/xieyihui/status/1020276542121947136)

<!-- -->


> **Aliakbar Akbaritabar (Ali)** (@Akbaritabar; 1/1): @syknapptic I am not sure if I am missing out on somethings or not, but from when I got in touch with #rmarkdown in #rstats, I remember this was provided in chunk options to define what language it is:
https://t.co/PozVrlQweX
>
example, I am putting Python chunks along R &amp; knitr does the rest  [&#8618;](https://twitter.com/xieyihui/status/1020357563857231872)

<!-- -->


> **Matt Crump** (@MattCrump_; 0/0): Most awesome! Check this out for all things RMarkdown. The Definitive guide!
https://t.co/yMKZXOIgnf https://t.co/c7gYD62hMQ  [&#8618;](https://twitter.com/xieyihui/status/1020410130108731393)

<!-- -->


# knitr

> **Ben Marwick** (@benmarwick; 4/0): @rctatman Often there are so many #rstats pkgs used in a project it can be hard to decide which ones to cite (do we cite knitr, ggplot2? usually those are not appropriate), here's some handy advice on that: https://t.co/b8JgUmsFSF  [&#8618;](https://twitter.com/xieyihui/status/1020482192248483840)

<!-- -->


> **Josef Fruehwald** (@JoFrhwld; 4/0): @jvcasill I’ve always found it charming that the command to extract the R code from a knitr document is purl()  [&#8618;](https://twitter.com/xieyihui/status/1020348371779883008)

<!-- -->


> **Aliakbar Akbaritabar (Ali)** (@Akbaritabar; 1/1): @syknapptic I am not sure if I am missing out on somethings or not, but from when I got in touch with #rmarkdown in #rstats, I remember this was provided in chunk options to define what language it is:
https://t.co/PozVrlQweX
>
example, I am putting Python chunks along R &amp; knitr does the rest  [&#8618;](https://twitter.com/xieyihui/status/1020357563857231872)

<!-- -->


> **Aliakbar Akbaritabar (Ali)** (@Akbaritabar; 1/0): @syknapptic my bad, sorry.
Confession: besides "echo=TRUE" &amp; "include=TRUE" to show source on how it works, I have never needed to show what was the engine the code was written in 🙈
I tried now as said in:
https://t.co/kttcej82zX 
with echo to show chunk options, it doesn't say the engine:(  [&#8618;](https://twitter.com/xieyihui/status/1020365916016717824)

<!-- -->


> **Brendan Knapp** (@syknapptic; 1/0): #rstats folks, 
>
Is there a knitr/rmarkdown/YAML option to annotate the language engine used for each chunk? Or just include the chunk options in the output somehow?
>
Something as "raw" as this would work:
>
\`\`\`{r} 
foo_R( )
\`\`\`
## R output
>
\`\`\`{python}
foo_Py( )
\`\`\`
## Py output  [&#8618;](https://twitter.com/xieyihui/status/1020350453152854018)

<!-- -->


> **Robert Sills** (@robertnsills; 0/0): Finalfit, knitr and #R Markdown for quick results - #PrescientInfo https://t.co/PxKxgPNYFE  [&#8618;](https://twitter.com/xieyihui/status/1020464267399696385)

<!-- -->


> **PossibilityUnlimited** (@Earriffic; 0/0): Finalfit, knitr and #R Markdown for quick results - #PrescientInfo https://t.co/9qoM6fhE5D  [&#8618;](https://twitter.com/xieyihui/status/1020431246651023360)

<!-- -->


> **Seth Axen** (@sdaxen; 0/0): It looks like the kind of workflow I'm thinking of is supported by R Markdown using knitr. Knitr also supports using Python to run chunks, and it natively uses pandoc (and pandoc-citeproc!) to generate outputs. Will give it a shot and report back. https://t.co/hE6NVlZmYL  [&#8618;](https://twitter.com/xieyihui/status/1020386769366233088)

<!-- -->


# xaringan

> **Matt Crump** (@MattCrump_; 2/0): Trying out the #xaringan package for using Rmarkdown to make presentations in HTML5 by @xieyihui Just discovered the infinite moon reader. Fantastic stuff!  [&#8618;](https://twitter.com/xieyihui/status/1020437677538193408)

<!-- -->


# yihui.name

> **Aliakbar Akbaritabar (Ali)** (@Akbaritabar; 1/0): @syknapptic my bad, sorry.
Confession: besides "echo=TRUE" &amp; "include=TRUE" to show source on how it works, I have never needed to show what was the engine the code was written in 🙈
I tried now as said in:
https://t.co/kttcej82zX 
with echo to show chunk options, it doesn't say the engine:(  [&#8618;](https://twitter.com/xieyihui/status/1020365916016717824)

<!-- -->


> **Colin Fay 🤘** (@_ColinFay; 0/0): @NicholasStrayer @daattali Tried it also a while back after https://t.co/rWkMSdDHNt 🎥 
Really fun  [&#8618;](https://twitter.com/xieyihui/status/1020388413340569601)

<!-- -->


