Ark: UI Comm: executeCode() should use something more precise than languageId

[DavisVaughan]

If you open two R sessions:

• One console R
• One notebook R

and then in the notebook R session you call rstudioapi::sendToConsole(), then that will hilariously send the text to the console R session rather than the active notebook R session.

This is a result of us using the languageId as our guide of where to execute the code, but that ends up always resolving to a console session, and never a notebook session.

positron/src/vs/workbench/services/positronConsole/browser/positronConsoleService.ts

Line 401 in 2e3827d

const positronConsoleInstance = this._positronConsoleInstancesByLanguageId.get(languageId);

It may also be the fault of our rstudioapi shims in ark. It is possible we should error if we detect that we are in notebook "session mode" rather than console session mode and we call an rstudioapi shim, like this in just a typical terminal R session

> rstudioapi::sendToConsole("hi")
Error: RStudio not running

[juliasilge]

I mean, rstudioapi::sendToConsole() did send the code to the console. 😆

[petetronic]

From Triage, can you help us understand what you're trying to do and the expected behavior?

[DavisVaughan]

I'm worried that anyone working in an ipynb or another notebook will run something that triggers an rstudioapi command in that notebook, but the command ends up getting executed in their Console R session rather than the Notebook R session

It is possible that in ark we just need to not allow parts of the rstudioapi like executeCode() if we detect we are in "notebook" mode rather than "console" mode, because in notebook mode there isn't really a console to execute in.

[juliasilge]

This will come up as we work on #3173