Time until R and time until autocompletion (blink.cmp)

[gueyenono]

Hello all,

I was wondering how long it took everyone to get from opening an R file to being all set to execute R code. As for me, it takes me about 10 seconds to start rnvimserver and another 10s to actually get the R console ready to run some R. Is this about how long it takes everyone?

Now, upon opening an R file, it takes me about 10 seconds until I get autocompletion for R packages (i.e. inside library()). I decided to go the blink.cmp way on my fresh neovim configuration. Is this something to be expected?

Thank you.

[jalvesaq]

Please, post the output of :RDebugInfo.

[gueyenono]

Sure thing, here it is:

before_rns.R stdout: (empty)
nvimcom info:
  Rversion: 4.5.0
  version: 0.9.69
  home: /nix/store/.../nvimcom
Time:
  global setup: 0.011482229
  check health (async): 0.010976183
  before_rns.R (async): 17.556997471
  unix setup: 0.002354958
stderr of last completion data building:

before_rns.R stderr: (empty)

[jalvesaq]

The times that I get when editing a Quarto document on my desktop computer (running Debian Linux):

Time:
  before_rns.R (async): 0.139488816
  pdf setup (async): 0.002389954
  global setup: 0.001920312
  rmd setup: 0.001379803
  check health (async): 0.001076516
  unix setup: 0.000816364

The before_rns.R time is about 100 times longer than the others. Yours is about 1000 times longer than the others. So, the problem doesn't seem to be in your Neovim configuration. RDebugInfo confirms that R is running very slowly. However, again, I'm unable to help because I'm on a different system. To have more information on the problem, you could try to run R manually within Neovim to see if it's faster:

:terminal R

[PMassicotte]

Which terminal/shell are you using? Maybe something in the *rc config that takes long?

[gueyenono]

@jalvesaq Thanks for getting back to me. Actually, :terminal R takes quite a bit of time too! Maybe because I'm on an Ubuntu server?

@PMassicotte I'm using Bash. My first experience with Neovim was with kickstarter.nvim. After using it for about a year, I now want to develop a new configuration from the ground up with the things that I want. I am currently doing it on an Ubuntu server. My .bashrc file mainly contains aliases, so I highly doubt it is the culprit here.

[PMassicotte]

@jalvesaq Thanks for getting back to me. Actually, :terminal R takes quite a bit of time too! Maybe because I'm on an Ubuntu server?

@PMassicotte I'm using Bash. My first experience with Neovim was with kickstarter.nvim. After using it for about a year, I now want to develop a new configuration from the ground up with the things that I want. I am currently doing it on an Ubuntu server. My .bashrc file mainly contains aliases, so I highly doubt it is the culprit here.

I am suspecting that it does not take long when you open R in your default terminal (i.e. outside nvim)?

[jalvesaq]

Actually, :terminal R takes quite a bit of time too! Maybe because I'm on an Ubuntu server?

Hence, probably it's not a R.nvim bug. The problem might be related to the server, but the time that a piece of information needs to travel from one machine to another could be measured in milliseconds, as we can see when browsing the internet.

[gueyenono]

@jalvesaq When I'm happy with my configuration, I'll clone it to my machine and let you know how it goes.

[gueyenono]

Alright folks, I finally ported my Neovim configuration over to my PC and the loading times are in line with those posted by @jalvesaq. I recently learned that there's a way to have multiple self-contained Neovim configs on the same machine (Advent of Neovim by TJ Devries). This is the way I should go from now on if I want to change things up a bit without affecting my main config.

[jalvesaq]

Thanks for the feedback, @gueyenono! I'm glad to know that R.nvim seems to be OK on your PC.