Nvim-R VS neoterm

If you do a lot of R coding, then a package more specific to R, and more fully featured is Nvim-R.

The whole reason I ended up going this route was also sort of data-science related: there’s a really spectacular R plugin for Vim, which I wanted to recapitulate as best I could when using python: https://github.com/jalvesaq/Nvim-R

I am slowly getting into using neovim. I am now trying to setup my R programming environment. I have successfully installed Nvim-R with Packer (https://github.com/jalvesaq/Nvim-R). Now, I would like to use the radian console (https://github.com/randy3k/radian/blob/master/README.md#nvim-r-support). In the documentation, it is said to put this in the config file:

But just wondering if people have tried using it with the Nvim-R plugin? I'm not sure it is worth the effort for me looking through the steps needed. Also, do I need to switch my init.vim/vimrc to lua? Perspectives appreciated!

However, there doesn't seem to be much available support yet for Quarto editing. The only plugin I could find is limited to syntax highlighting. To my knowledge, Quarto also isn't a built-in filetype yet. I've worked around this by manually creating a filetype and using R Markdown syntax highlighting with the Nvim-R plugin, which lets me send R code in chunks to a REPL and see results while I edit. Nvim-R also supports evaluation of Python code chunks using an R package that evaluates Python code, but that's not an ideal solution for editing a Python-only file.

looking for a neovim plugin that's similar to Nvim-R, but for python.

For that reason, I want to use Nvim-R in combination with ncm-R. I get the completion to work if I use it manually with Ctrl+x Ctrl+o, but it does not start automatically. My init.vim file looks like this:

I use Nvim-R. It took a bit of time to learn the key bindings, but the documentation is pretty clear.

If you want to go in a very different direction, you can try vim (or neovim) with nvim-r. For a variety of reasons, that’s what I tend to use.

nvim + Nvim-R user here as well.

I use Vim with neoterm, highly recommend. - guaranteed support on everything with a repl - never creates unexpected windows - every interaction is explicit

At the moment I am planning to write two modules and then start on 'mini.terminals'. I usually prioritize work based on combination of "I have some cool idea about this" and "I don't like what I am currently using". I am using kassio/neoterm for a very long time and it is quite OK for my needs.

Neovim works just fine. I use Neoterm to send-to-repl, here's what my config looks like. Your other options include vlime and slimv. I switched to neoterm because it's simple, explicit, and doesn't create unpredictable windows. Works for any other language just as well.

Using neovim + https://github.com/kassio/neoterm I have a similar, possibly simpler, workflow that doesn't require any other program (especially listening willy nilly with no authentication/authorization whatsoever) other than your normal SQL client running:

* I open a :Term window, in which I run the sql client (i.e. ":Texec sqlite\ foo.sqlite" or ":Texec mysql foo", etc)

I'm using neoterm. I like that I can use the same tech for every language + consistent keybinds. Also Slime might not support a more fringe or outdated lisp distro but a plain old VTY terminal always will.

I've been using Neoterm, coupled with its vim-test strategy, for this

Having gone from a stock vim to a highly modified vim and back again, here are some plugins that I find really boost my productivity:

- neoterm, for opening a REPL in a split buffer and quickly sending chunks of lines to the REPL (https://github.com/kassio/neoterm)

- fzf for faster buffer and file navigation (https://github.com/junegunn/fzf.vim)

- vim fugitive for good git integration (https://github.com/tpope/vim-fugitive)

- some other tpope plugins (surround, unimpared, commentary, vinegar)

I found Vlime to be more updated than slimv and give a smoother experience. With time I've switched to bare neoterm which I highly recommend. CL and lisps in general are designed with a text repl in mind, so this is the method that is guaranteed to work on every obscure CL distribution, and also transfer well to any other REPL-based languages.

I start terminal inside of neovim. It works really well. In this terminal, you can use gf (goto file) keybindigs, etc. It works especially well with this plugin: https://github.com/kassio/neoterm

Workflow is basically to open two windows (left with code, right with terminal) and send code from left window to right with a help of kassio/neoterm.