REditorSupport / REditorSupport/vscode-R

R extension warnings: system cannot find the path specified and Failed to get list of R functions

Open
#1,307 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.2k
Forks
139
Avg merge
2h 46m
Merged PRs (30d)
5

Description

Describe the bug
R extension of vs code reports two warning notifications every time that my cursor moves over a R code ,that say:

  1. The system cannot find the path specified.
    2.Failed to get list of R functions. Make sure that jsonlite is installed and r.rpath.windows points to a valid R executable.

I can still run R code, but those warnings are annoying and I don't know if something is wrong that I'm not noticing. I already have the jsonlite package installed in R and R path set on the vs code settings.

To Reproduce
Steps to reproduce the behavior:

  1. Open or write any R script
  2. Move the cursor over any function of the code.
  3. See error

Can you fix this issue by yourself? (We appreciate the help)

No

(If applicable) Please attach setting.json

{
    "workbench.colorTheme": "Visual Studio Dark",
    "[python]": {
        "editor.formatOnType": true
    },  
    "files.associations": {
        "*.rmd": "markdown"
    },
    "r.bracketedPaste": true,
    "r.rterm.windows": "C:\\Users\\Dell\\AppData\\Local\\Programs\\Python\\Python311\\Scripts\\radian.exe",
    "r.rpath.windows": "C:\\R\\R-4.2.2\\bin\\x64\\R.exe"
}

Expected behavior
I excpected to be able to work with R in vs code

Screenshots
If applicable, add screenshots to help explain your problem.
image

Environment (please complete the following information):

  • OS: Windows (64 bits)
  • VSCode Version: 1.75.1
  • R Version: 4.2.2
  • vscode-R version: 2.7.1

Additional context
Please, help. I will aprecciate it

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the warnings from the issue with the listed Windows, VS Code, R, and vscode-R versions, using the provided settings and cursor-hover steps. Determine which R function lookup or executable invocation produces each warning; done means the warnings no longer appear while working with R code and existing R execution still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, typescript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.