Recommended setup for rnoweb files when using R.nvim and vimtex in parallel

[simongrund1]

Dear all,

recently, I've encountered some issues with rnoweb files, where nvim would occasionally freeze upon triggering auto-completion. My configuration uses both R.nvim and vimtex for R and LaTeX, and completion for the latter is provided by nvim-cmp. This has worked well so far, but recently I've found that completion actions for LaTeX commands in rnoweb files reliably freeze nvim when triggered in quick succession (e.g., when I write out a LaTeX command and delete it by holding backspace).

The issue does not occur if I disable the R.nvim completion engine:

r_ls = {
    completion = false,
    hover = false,
    signature = false,
}

It also does not occur if I kill rnvimserver before triggering the completion actions that would normally cause a freeze, which makes me think they conflict somehow. In the docs, it is recommended to not run R.nvim's completion engine in parallel with nvim-cmp, which seems consistent with this but also makes me question my config.

Is there are recommended way of configuring R.nvim that gives me auto-completion for both the R and LaTeX bits in rnoweb files or a way I can apply the config above selectively depending on filetype?

Thanks for the input!

Simon

[jalvesaq]

I'm not sure if anyone actively involved in the development of R.nvim edits Rnoweb files.

Does the bug happen without vimtex?
Could you please post a complete minimal setup to replicate the bug, including nvim-cmp, vimtex, etc...?

[richardsc]

I'm a big user of Rnw and R.nvim and will give this a test when I'm at a computer later. I haven't noticed this behaviour, but I have used blink for nearly a year instead of nvim-cmp. I'm not a developer, but would be happy to learn how to contribute if it keeps my Rnw workflow happy.

[PMassicotte]

Can you provide a skeleton for a Rnw file? I will try on my side to replicate your issue.

[simongrund1]

Hi all, thanks for the replies. I did some additional testing and found that the issue is likely linked to one of the completion sources for cmp (cmp-nvim-lsp), which I had used in the past and which was still part of my config. The freezing occurs only when this completion source is loaded and does not occur otherwise.

The config I needed to reproduce this isn't really minimal, but I've zipped up the most minimal config I could (nvim.zip, contents of ~/.config/nvim). I can trigger the freeze with the following .rnw file, if I enter insert mode after the \textbf{} and hold backspace. The freeze can be avoided by editing the plugins.lua to either remove the two references to cmp-nvim-lsp or adding the options mentioned above.

\documentclass{article}

\begin{document}

\textbf{} 

<<>>=
x <- 1:5
mean(x)
@

\end{document}

I'm not sure if this is at all specific to R.nvim, and the obvious solution for me is to not load cmp-nvim-lsp. However, I'm still curious if it is a relevant issue, because I observed it only with .rnw files. There seems to be something going on behind the scenes that I don't understand, so I still appreciate any input from the knowledgeable people here.

Edit: I should add that, when I use this setup, I don't get any autocompletion as I type. In .r files, I still get completions with <C-x><C-o> but no autocompletion from cmp. In .rnw files, I get nothing. I'm not set on cmp, so I appreciate recommendations of any kind.

[jalvesaq]

I can't replicate the bug with your nvim.zip configuration directory. Pressing <Backspace> after \textbf{} starts to complete textbf after {} is deleted. The completion menu has only one item:

 textbf  Text [cmd: default]