Stuck on an issue?
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.
R path not working
See original GitHub issueError message
R path not working:
/usr/bin/R
using the docker image rocker/r-ver:4.0.0.
Desired
Ideally the debugger would look for R in the PATH and not just at a single location.
Workaround
ln -s /usr/local/bin/R /usr/bin/R
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
'R path not working: /usr/local/bin/R (Can be changed ... - GitHub
framework/Versions/4.1-arm64/Resources/bin/exec/R (notice the exec directory near the end of the path). When I set that executable as r.rpath.
Read more >Setting Up Visual Studio code to work with R - "win32 can't ...
In "Search Settings" type "R". Enter the RPath determined in #1 above, then Ctrl + S to save.
Read more >Path does not exist? - R Markdown - RStudio Community
First verify that the file exists. Then, try with the absolute path of that file. Do you get same error then? @FinnW, in...
Read more >Command Line Interface (CLI) - Visual Studio Code
Note: Users on macOS must first run a command (Shell Command: Install 'code' command in PATH) to add VS Code executable to the...
Read more >Creating relocatable Linux executables by setting RPATH with ...
However, if the same executable were moved onto a different machine, or simply a different folder on the same machine, the “library not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ManuelHentschel Yes, we should remove the default paths as did by https://github.com/Ikuyadeu/vscode-R/commit/3b59667e40fcbb624adbc7fe373eeeaf8e8a798f#diff-b9cfc7f2cdf78a7f4b91a753d10865a2 in vscode-R.
I added a note that blank settings indicate that
PATHis used and a check for an empty string (done after searching the PATH/registry).This way the user should never see an empty path as error message but rather the (non-working) path or a message that no path was found at all.