languageserver VS neoterm

I'm not familiar with data science, but I would start with setting up a language server for R: https://github.com/REditorSupport/languageserver . Kate already have a default client configuration for it, so it should work out of the box.

Symbol outline by LSP Client: It can connect to any LSP "server" (runs locally) which implements LSP protocol (https://microsoft.github.io/language-server-protocol/), and supports "stdin" communication. A number of LSP server configuration is provided by default (including R), but user can extend, and override this configuration. As long as the LSP servers are properly installed (kate will start them) and the Kate LSP client configuration is set up properly should work. LSP also provides other IDE-like features (like code completion, jump to symbol definition, diagnostic/linter messages) etc. I found an LSP server for R (https://github.com/REditorSupport/languageserver), you may want to give it a shot.

You'd need: - hrsh7th/nvim-cmp with set up LSP source (hrsh7th/cmp-nvim-lsp). - neovim/nvim-lspconfig. - R language server installed. This is a regular R package, can be installed from CRAN.

Installed languageserver in R.

Lsp server for R like py-right for python. Check this

I have downloaded the language server from here https://github.com/REditorSupport/languageserver, but don't know where it put it. so form now it's in the "R\R-4.1.3\bin".

Besides a common modern Neovim "IDE setup", some other useful R-specific tools: - languageserver R package for LSP integration. - styler R package for code formatting. Somewhat slow and lacks some features, but seems to be the best current solution.

First of all, make sure that you actually use r_language_server. For that, at least install languageserver R package (run R from command line and execute install.packages("languageserver")) and set up r_language_server with nvim-lspconfig. I think after that you should be able to see some diagnostic information.

The truth is that most editors will use R language server underneath ( https://github.com/REditorSupport/languageserver ) so it's more what layout you prefer than what functionalities an editor has to offer.

Other plugins/utilities can fill in some of the other gaps. In the screenshot below, I'm using NvimTree to browse files, and I'm also currently using Neovim's native LSP client (in Neovim 0.5.0) with r_language_server installed (configured with the Neovim team's plugin nvim-lspconfig).

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.