REditorSupport / REditorSupport/languageserver
lintr diagstic support in Docker / remote servers (just by file content)
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 675
- Forks
- 118
- Avg merge
- 1d 37m
- Merged PRs (30d)
- 11
Description
I set up my r studio environment through Docker. You can find my setup here: https://github.com/LumaKernel/luma-r-env.
I'm now configuring r language server like with following:
lspconfig.r_language_server.setup {
cmd = { 'docker', 'exec', '-i', 'luma-r', 'R', '--no-echo', '-e', 'languageserver::run()' },
}
(This is configured by lspconfig, but not the essential for this issue)
And I will get the error:
Diagnostics:
Failed to run diagnostics: ! in callr subprocess.
Caused by error:
! Linter 'object_length_linter' failed in /Users/luma/foo.R: path[1]="/Users/luma/foo.R": No such file or directory
Yes, there's no such file in the container. Lintr seems invoked as like lintr('/Users/luma/foo.R') but in the server side.
Other features like hover on functions seem working.
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
The issue names an R language server configuration and lintr diagnostics, but no repository files or tests. Reproduce the Docker setup with the shown command, then trace how diagnostics pass the host path to lintr; done means diagnostics can run from file content when the path is absent in the server container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, r
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100