Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
path setting does not work on windows
See original GitHub issueNOTE: Before submitting an issue, please make sure to install the latest version of both the vscode extension and the R package. This can usually be achieved by running the command r.debugger.updateRPackage in vscode’s command palette (F1).
Describe the bug
on windows we need the extra & sign in front of the executable path in order to launch R, which is handled properly by the R extension bu not by r-debugger extension.
Previously there’s the separate rdebugger.rpath setting which could be set to & "z:\path\to\R.exe" to overcome this issue, but from some version on this setting is deprecated.
To Reproduce Steps to reproduce the behavior:
- set rpath to
z:\path\to\R.exe - launch anything from this extension (could be “install or update packages” or launch an r debugging task)
- See error
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry, I forgot to make update to this thread. It’s okay to close it, I eventually resolved it by unsetting rpath in vscode and setting environment variable prior to launching vscode
@xinstein Any updates on this issue? If not I’d close this as stale, since we could work out @gwd999 's problems in a separate issue.