neoterm VS toggleterm.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.

As a data point, I'd like to chime in here. I have been a 15 year user of tmux (and screen before that) and never thought I'd change my development habits. Over the holidays I decided I would do one of those once-every-five-years upgrades to my vim setup as I had accrued dozens of vendored plugins in normal vim and wanted to see what the big deal with neovim was.

I bit the bullet and evaluated some of the "distributions" (AstroNvim and kickstarter) and played around with all the new lua plugins that I had never thought I needed (why use telescope when FZF-vim worked so well?).

Anyways, after a month of tweaking and absorbing, I found myself running Neovide only, and doing something I never thought I'd see, running tmux from within neovim/neovide. I think this only works (for me) because of session management (there are half a dozen plugins for handling quickly changing 'workspaces') and because the built-in terminal (with a very useful plugin called toggleterm: https://github.com/akinsho/toggleterm.nvim) works so well.

I have not stopped using tmux and layouts, and it sits in another fullscreen iterm2 workspace, but I find that I now spend 90% of my time using a fullscreen neovide and summoning/toggling tmux momentarily for running commands.

Of course, the caveat here is that my preferred mode of operation is being fullscreen as often as possible. I think if your preferred mode of operation is to always see splits then running neovim from the terminal within tmux is still the way to go.

As for why I like neovide? I find the animations, when tweaked to be less 'cool' are extremely useful to see where the cursor jumps to. I am also a huge fan of the fact that I can finally use 'linespace' to put some space between my lines of code -- it is an aesthetic I didn't realize I wanted.

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 just found toggleterm which feels awesome. Pretty much exactly what I was looking for to use with Alacritty but even better since its integrated into the rest of my Neovim workflow.

I saw this plugin that tells me how to do it, however I got confused after I added "require("toggleterm").setup({})" in the lazy.lua file and installed the package as well using the Lazy command

I tried toggleterm but I wasn't successful.

And I never really got into Gitsigns or vim-fugitive. Lots of people love them, so I'm sure they're great, but I'm happy opening a floating terminal with Toggleterm and using Lazygit.

I agree with u/Bamseg, but you can get what you want using toggleterm.nvim BUT NOT IN FLOAT.

I use gitsigns for linewise operations (blame, reset, etc), and a floating terminal (toggleterm) for everything else. flatten.nvim also helps with nested nvim instances.

but I ended up finding a good enough workaround by using Lazygit through Toggleterm.

Perhaps you want something like https://github.com/akinsho/toggleterm.nvim and make a custom profile? Remapping a key for each extension seems fine as well, just remap it per-buffer inside of on_attach