r-markdown

I'm using RStudio 0.98.1103. It is said in release notes that they've added "Syntax highlighting modes for XML, YAML, SQL, Python, and shell scripts." But when I write something like this: ```{r engine='python', highlight=TRUE} print("Hello World") ``` - I don't get proper highlighting (like I have here). I've seen this question: Syntax highlighting for Python chunks does not work - but I guess it was asked before the release of 0.98.1103 and things could've change, I'm just doing something wrong. Could anyone help me out? output: html_document: highlight: pygments in the head did the trick.

I have the following installed: preview release of RStudio, Version 0.98.864 (May 24th, 2014) development versions of knitr and shiny, via devtools::install_github(c("yihui/knitr", "rstudio/shiny")) I would like to create a Shiny Presentation (RStudio menu items: File>New File>RMarkdow>Shiny>Shiny Presentation) with custom CSS but am unsure how to do so. My custom CSS (which currently only changes the colour of header 2) h2 { font-size:1.8em; color: red; } works with an extract of an example given on the RMarkdown PResentations with ioslides webpage : --- title: "Habits" author: John Doe date:

I am using rmarkdown, pandoc and knitr to create a pdf including chunks of r code. Within a code chunk I have a for loop which prints a number of graphs and some statistical output. I would like to insert a page break into the loop (to appear in the pdf output). This page break would occur after each graph is printed, to ensure each graph is printed on one page and the statistical output on the next. I have been unable to find a way of including a page break in my r code chunk. I have tried cat("\\newpage") and cat("\\pagebreak") in the hopes it would be recognized by pandoc but to no avail

I have a simple question, and I think I'm just not looking in the right place, or RStudio is not acting as expected. I'd like to know if there is an option to output the results of all my markdown code chunks to go to the plots window or the console. I'm starting to use R Notebooks to write in R Markdown. Say I type the command head(cars) into my .Rmd document. I press Ctrl + Enter, and the line is run. Up pops the first 6 lines of the cars dataframe into my script. I see that the line has been run in the console, but the output is not in the console. Why does this bug me? Sometimes my code

One of the promises of the bookdown package is functions for automatic numbering of figure/table captions, and cross-referencing figures/tables/sections. This is claimed to be enabled for single-Rmd bookdown, if we use bookdown::html_document2 in the YAML: https://bookdown.org/yihui/bookdown/a-single-document.html Looking at the raw rmarkdown for that chapter of the bookdown manual, I've tried to follow the instructions to make a single Rmd file that can use those cross-referencing functions. But I can't get it to render as expected, with cross-references. Here's a simple example Rmd: ---

I am trying to add and resize a local image to a .Rmd file in RStudio that will produce a pdf. I can add the file easily with  but I have not figured out how to control the size of the image. I tried HTML code with a width attribute, but the image would not appear (I think this only works if outputting to HTML). <img src="path/file.png" width="200px" /> I could not get this idea to work:  Is there a way to modify the Rmarkdown script to modify the size of the local image with only RMarkdown and base R? There is a suggestion to use

I am operating matrices with R 3.1 and RStudio 0.99. I have my R Script and with cmd+enter it works without problem. I created an Rmd for reporting but I have this error Error in lazyLoadDBinsertVariable(vars[i], from, datafile, ascii, compress, : long vectors not supported yet: ../../../../R-3.3.1/src/main/connections.c:5600 Calls: <Anonymous> ... <Anonymous> -> <Anonymous> -> lazyLoadDBinsertVariable Execution halted Is there a way to bypass that error? This seems to be a dupicate of Large Matrices in R: long vectors not supported yet but the difference is that this only happens when trying