You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if that's a bug or an expected behavior. Let's say you have the following .Rmd file:
```{r}
a <- stop()
```
```{r}
x <- a + a
```
```{r}
str(x)
```
If you go to the line with str(x) and run "R: Run Above Chunks", it will start running all of them, despite the fact that R breaks on the first chunk already.
Is that an expected behavior? Is there an option one could use to stop on the chunk where it breaks?
Basically, I'm trying to understand how to debug large Rmd files, where things could break early in the report.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Not sure if that's a bug or an expected behavior. Let's say you have the following
.Rmd
file:If you go to the line with
str(x)
and run "R: Run Above Chunks", it will start running all of them, despite the fact that R breaks on the first chunk already.Is that an expected behavior? Is there an option one could use to stop on the chunk where it breaks?
Basically, I'm trying to understand how to debug large Rmd files, where things could break early in the report.
Beta Was this translation helpful? Give feedback.
All reactions