Suggestion: Document current R debugging workflow and limitations? #9586
-
|
While switching to Positron for R development, I struggled to understand how to enter a debugging session. The UI led me down an incorrect path that suggested I needed extensions. After trying this path, I only found the solution through external (To the Positron site and docs) resources:
Suggestion: Could the Positron website include a brief R debugging section covering:
This might help users avoid the confusion I experienced and set proper expectations while the R debugger evolves. Once I understood how to initialize debugging, the interface was familiar enough to navigate. Would this be appropriate as a documentation enhancement issue? Or is this already being addressed internally/deemed as not necessary at this time? Session Info─ Session info ───────────────────────────────────────────────────────
setting value
version R version 4.5.1 (2025-06-13 ucrt)
os Windows 11 x64 (build 22631)
system x86_64, mingw32
ui Rgui
language (EN)
collate English_United States.utf8
ctype English_United States.utf8
tz America/New_York
date 2025-09-25
pandoc NA
quarto NA @ C:\\Users\\harrism1\\AppData\\Local\\Programs\\Quarto\\bin\\quarto.exePositron Version: 2025.09.0 (user setup) build 139 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Thank you for this suggestion, which I definitely agree is important! 💯 We are still working on the debugger for R and have been waiting to document it until it is a bit more complete.
|
Beta Was this translation helpful? Give feedback.



Thank you for this suggestion, which I definitely agree is important! 💯 We are still working on the debugger for R and have been waiting to document it until it is a bit more complete.