-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plain Code Blocks in RMarkdown #252
Comments
Similar for me; I get the same error. I have some non-R fenced blocks in my rmd-file, eg.,
(This code blocks are taken from bookdown) |
Disregard this issue; I now wrap plain-code-blocks in a "~~~~" block and the Malformed file bug doesn't come up in lintr (I couldn't pinpoint the problem within lintr or it's dependencies though)
|
I think we should keep this issue opened until it is probably addressed. |
Do you think this relates to the #322 bug whereby lintr parses non-R code blocks (eg, embedded bash / python) as if they were R code? |
It is a different bug. At least a python block doesn't throw |
I've submitted a PR to hopefully fix this. |
I have an issue when running lintr (v1.0.0 in vim or within R) on Rmarkdown files that contain plain code blocks (as defined here). Running lintr on the following (temp.Rmd) throws an "Error: Malformed file!", despite plain code blocks being legal in Rmarkdown and lintr working fine on any other Rmarkdown files that contain R code. If the block containing "This isn't evaluated" is removed, lintr runs fine; when it's present, the Malformed file error comes up.
---
title: "Plain Code Bug?"
output: pdf_document
---
```{r}
42
```
```
This isn't evaluated
```
The text was updated successfully, but these errors were encountered: