REditorSupport / REditorSupport/languageserver
Autocompletion Slow
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 675
- Forks
- 118
- Avg merge
- 1d 37m
- Merged PRs (30d)
- 11
Description
Hi,
I'm using VSCode on a remote machine (a university cluster) and I am experiencing slow autocompletion in the VSCode editor with the R extension. When I type, no autocompletion is suggested, then after pressing Ctrl+Space, I see a message that says "Loading", which it will do for about 20s and then autocomplete works smoothly for a bit (1-2 min), then eventually the same thing happens and I have to reload (maybe after being idle for some number of seconds). I've been reading for hours online trying to see if there's anything from similar issues that might help, but so far they haven't worked. I tried disabling all extensions besides R and changing the R>LSP: Args to "--vanilla and --no-init-file". I have all the suggestion settings enabled and based on the Ctrl+Space behavior it really seems like the problem is that it takes a long time for the suggestions to load. I'm guessing a call is made to load R and I wonder if that's really slow for some reason.
When I look at the logs of languageserver, I see that it's loading a lot of my R packages, which has got to be the reason it takes a long time to load. Maybe it's because it's trying load all the packages listed in my R file (or all R files open in the editor?). That would be okay with me if it was done once automatically the first time a suggestion is attempted. But that's not the behavior I am observing. Is there a way I can achieve this behavior or do you have any advice to reach this goal of having smooth autocompletions?
Thanks,
George
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 report mentions VSCode remote use, the R extension, and languageserver logs but names no repository file or test. Start by reproducing the delayed completion and inspecting those logs while testing the reported settings. Done would require a confirmed cause and a documented fix or clear guidance for smooth completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100