REditorSupport / REditorSupport/languageserver

Cannot manage to trigger completion on ,<space> or $

Open
#360 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
675
Forks
118
Avg merge
1d 37m
Merged PRs (30d)
11

Description

Hello, first, many thanks for implementing language server in R it works great and out of the box !

I use languageserver in vim via coc-r-lsp and in combination with nvim-r. Completion works fine when triggered by ( or , but I tried to setup completion after ,<space> with no success.

I asked a question here and I understand that completion should be provided by the server.

As per documentation, I added the following to my .Rprofile

options(languageserver.server_capabilities = list(                                                 
        signatureHelpProvider = list(triggerCharacters = list("(", ",", "$"))),                    
        completionProvider = list(resolveProvider = TRUE, triggerCharacters = list(".", ":", "$")) 
)                                                                                                  

But I cannot get any completion after ,<space>, would you have some pointers for me ?

PS: please not that I tried to get completion of data.frame columns too and could not get it to complete either

Contributor guide

No contributing guide indexed for this repository

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 completion in Vim with coc-r-lsp and nvim-r, using the .Rprofile server_capabilities configuration shown in the issue. Check behavior after comma-space and for data.frame columns, then compare it with completion triggered by (, comma, or $. Done means the reported completion cases work through the R language server.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.