neoterm VS vim-floaterm

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.

Using https://github.com/voldikss/vim-floaterm and remap the same shortcuts to (un)toggle the terminal would be interesting for you, also about compatibility, because if tomorrow you use nvim in the terminal you have the same key maps.

vim-floaterm has wrappers around some terminal filemanagers.

If you don't like distro's and want to use something of your own, make sure that you have a few plugins like telescope.nvim, lazy.nvim, toggleterm.nvim Or vim-floaterm, gitsigns.nvim, which-key.nvim, which will make your neovim journey smooth. Again these are just few, but I highly recommend it.

My personal favorite is ranger, a multi-panel console file manager that works nicely in a Neovim terminal. I also use floaterm to get floating terminal windows for ranger and lazygit, but that's optional. A Neovim tab with a terminal would work equally well.

For simple tasks like opening a dirty file in nvim I prefer vim-floaterm. It has a really nice integration with a bunch of TUI tools.

The two obvious candidates are vim-floaterm and toggleterm.nvim.

I’d suggest taking a look at vim-floaterm. While I don’t use this feature, it should have the ability to do what you’ve described

vimwiki + floatterm + vimwiki-sync