How to get multiline execution like R studio

[AustinNashSci]

Hello,

In R studio a ctrl enter on multiple lines of code would execute all lines of code, while in Positron it does not execute these lines, which makes running R scripts tedious.

How can I get the same execution behavior as in R studio?

Example: A single ctrl enter execution at the prediction line would execute log(a+b+c) in Rstudio, but in positron it hangs at log(a+

a = -0.25
b = -1
c = 1
 
prediction = log(a +  
                            b +
                             c)  

[LibbyHeeren]

I wasn't having a problem using cmd+enter running multiple lines (with my cursor on any line of piped-together code) until this morning. Now, Positron (or quarto?) is only running the line my cursor is on. Sounds like we're seeing the same thing.

[juliasilge]

We've had some folks report problems like this in #7589.

• Can you look at what keybindings you have defined as described in Command-Return in quarto document doesn't execute #7589 (comment)?
• If you get into this state, can you try out the steps outlined here, to see what is/isn't working? Command-Return in quarto document doesn't execute #7589 (comment)

[ateucher]

I've been experiencing something similar intermittently, in regular .R files as well is in Quarto cells. It sometimes gets into a state where it doesn't seem to detect that it is in a block of code that should be executed together. This happens like @LibbyHeeren reported in a series of piped statements, also if my cursor is on the last } closing a function definition, etc. This state is often accompanied by a state where completion suggestions stop showing up. I can't reliably reproduce it, but I was teach a workshop yesterday where participants reported experiencing the same thing.

The next time I find myself in that state, what can do/look for to help diagnose the issue?

[ateucher]

To note - restarting my R session doesn't seem to fix the issue, but closing and reopening Positron usually does.

[louhao1129]

I have occasionally encountered similar problems as well.

[juliasilge]

Thanks so much for these reports! 🙌

It sounds to me like the LSP is going down or getting disconnected somehow and the statement range provider does not come back up afterwards as outlined in #9069. If any of you get into this state again, can you try this in your .R or .qmd, to see what you observe:

• Does the "Run cell" command work as expected in .qmd?
• If you put your cursor, say, in the top line of a multiline statement and run the Quarto: Run Current Code command from the command palette, what happens?
• Can you open the output channel that has a name like "R 4.5.1: Language Server (Console)" and see what is going on in those logs?
• If you run Developer: Reload Window does the behavior fix itself after the window reloads?

[ateucher]

Oh that does make sense, this feels very much like #9069 (and #9317). Thanks, I'll keep a closer watch

[ateucher]

I can reproduce this by restarting extensions.

Then in a new R file I put:

library(dplyr)

mtcars |> 
  filter(cyl == 6) |>
  summarise(avg_mpg = mean(mpg))

When I put my cursor on the first line and press CMD+Return, it only sends mtcars |> to the console.

When I go to inspect the output channel R 4.5.1: Language Server (Console), that output channel is actually gone:

When I run Developer: Reload Window, the R Language Server output channel is back, and the code is sent to the console in a block as expected.

Here's a screen record of the whole process:

Screen.Recording.2025-10-20.at.2.08.51.PM.mov

[juliasilge]

When I go to inspect the output channel R 4.5.1: Language Server (Console), that output channel is actually gone

‼️‼️‼️

I had not noticed this before.