R debugger: starting debugger prompts file saving

[EmilHvitfeldt]

Positron Version:

Positron Version: 2023.10.0 (Universal) build 1453
Code - OSS Version: 1.83.0
Commit: b781e9e
Date: 2023-10-30T03:03:08.650Z
Electron: 25.8.4
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 22.6.0

Steps to reproduce the issue:

1. make debugger happen in unsaved file.

I ran

debugonce(lm)

lm(mpg ~ disp, data = mtcars)

Kapture.2023-10-30.at.21.33.51.mp4

What did you expect to happen?

For this prompt not to happen

Were there any error messages in the output or Developer Tools console?

Nope

[DavisVaughan]

I'm not sure if this is a good or bad thing tbh!

On one hand, being in a debugger state is inherently a little unstable regardless of what language you do it in, so encouraging a saved file seems reasonable.

On the other hand, I often want to quickly debug something in vctrs so I'll open a new scratch file, type in some code that i know will trigger the issue, run debugonce(fn) in the console, then run that code in the scratch file, and saving seems like overkill there

---

I think I convinced myself we should look into avoiding this save prompt, because of how often I do the "quick debug" in a scratch file

[DavisVaughan]

See microsoft/vscode#77023 where Debug: Save Before Start is mentioned as an option to control this, I think that should help