REditorSupport / REditorSupport/languageserver
VS Code weird startup error: `radian: error: no such option: --no-echo`
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 675
- Forks
- 118
- Avg merge
- 1d 37m
- Merged PRs (30d)
- 11
Description
So, I am not sure how this affects language server, or if it does at all.
I get this at startup:
R Language Server (973951) started
Usage: radian
radian: error: no such option: --no-echo
R Language Server (973951) exited with exit code 2
Everything seems to be working well though.
I have both r.rterm and r.rpath pointing to radian
Should I have one of them point to R?
In another post I was reading about r.path.lsp but that does not seem to be an available option.
I am using the R Editor extension on the latest VS Code
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the VS Code settings referenced in the report, especially r.rterm and r.rpath, and reproduce the R Language Server startup with radian. Determine why --no-echo is being passed to radian; done means the language server starts without the option error while the existing R integration continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100