vim-slime VS neovim-remote

https://github.com/jpalardy/vim-slime

you can have a REPL in nvim/vim/tmux/screen/another terminal/or any other window , and send regions from your vim buffer to that repl

For vim users, check out vim-slime[1]. It's really changed my workflow! It can work for any language that uses a REPL, including bash/shell. Combined with tmux, it is an amazing and (in hindsight) obvious tool. I honestly can't imagine myself going back to not having it now.

[1]: https://github.com/jpalardy/vim-slime

For splitting the terminal you could try either toggleterm or tmux. If you want to send things from one tmux pane to another, then you can use slime. For a toggle-able filetree, you can use nvim tree.

I use vim-slime. It works really well in tmux. https://github.com/jpalardy/vim-slime. Just blocks of code as cells

This is yet another plugin to capture text from the current buffer and send it to a tmux pane. I was using https://github.com/jpalardy/vim-slime previously, and wished I could just set sensible defaults for where to send text. Also, I wanted to create my first Neovim plugin! I have to say, after writing a bit of Vimscript in the past, the Neovim Lua API makes me a much happier camper.

I use slime (which sends code to tmux panes), tmux (of course) and ipython for this. For example, the code I sent to ipython was with a simple keybinding ...

If I understand correctly, what you need is a combination of vim, tmux, ipython and vim-slime.

REPL??? Do you have a very-easy-to-use way of running and testing your code? From vim-slime to nvim sniprun to autocommands with the built in terminal, to an external repl like ptpython (for python obviously). iron.nvim and conjure are two other neovim repl plugins. There are many ways of running the code that you're working on, and having something that makes this really easy for you is pretty essential. (sometimes I use inotifytools on linux to literally just run the script every time I save it.)

For the record/list, there's also: - https://github.com/hkupty/iron.nvim and - https://github.com/jpalardy/vim-slime

However, if you're coding in an interpreted language like python, R, bash, etc., then there is one plugin which you are likely to find helpful. That's vim-slime.

Notice that this script depends on mhinz/neovim-remote: Support for --remote and friends. (github.com). (nvr as you have notice). The full-path is required to make it work.

I am currently using https://github.com/mhinz/neovim-remote with this bit in my zshrc:

Since they are on different screens I cannot use a single neovim instance (I tried playing around with neovim-remote but seems like that's for the usecase of opening files in one instance from different terminals -- doesn't help). Due to multiple LSP instances changes in one file are not reflected in the other, e.g., file B imports some types from file A; I create a new type in A but since B's neovim instance is not aware of any change to the A file corresponding the LSP fails to see the new type.

This version includes `nv` binary which is [neovim-remote](https://github.com/mhinz/neovim-remote) but rewritten in Rust (I've did it out of boredom) also with interface similar to `page`.

Practical use case: when navigating in ANY terminal (or tmux) write a function that sends opened files to a single running neovim instance instead of spreading opened vim instances all around like neovim remote does, but works for any terminal

I see the integration with neovim is done via a separate plugin, did you think about adding support for neovim-remote?

Another way of doing what u/TheLeoP23 suggested is by using https://github.com/mhinz/neovim-remote . This way you have a single neovim instance and you can open it on different terminals and mantain your current workflow.