neoterm VS magma-nvim

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.

You use magma-nvim for interactive jupyter experience (or my fork which also includes three last PRs)

FYSA: https://github.com/dccsillag/magma-nvim & https://gitlab.com/usmcamp0811/nvim-julia-autotest

Check out Magma.. it works with Julia.. see my open PR for examples... does require IJulia.

Just throwing this out there... cause its pretty cool!! https://github.com/dccsillag/magma-nvim

I use them all the time and there are many features that differentiates it from vim, which is why I asked for clarification. In any case this plugin is pretty sweet if you want to evaluate cells within vim: https://github.com/dccsillag/magma-nvim

Have you taken a look at https://github.com/dccsillag/magma-nvim?

My current workflow is a combined version of Maxwellrules' solution and magma.nvim. I am mostly satisfied. I could maybe use vim-jukit's cell division, but otherwise I am good for now. Though again: I am definitely open for better solutions.

You can check out https://github.com/dccsillag/magma-nvim A nice, integrated solution in my opinion.