toggleterm.nvim VS FTerm.nvim

akinsho/toggleterm.nvim: A neovim lua plugin to help easily manage multiple terminal windows.

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.

To achieve our goals of fingertip access nirvana, we are going to be using a plugin called FTerm.nvim.

i use F2 to toggle Fterm

IIUC this request https://github.com/numToStr/FTerm.nvim/issues/67 is also similar to your use case. I might implement this in FTerm.nvim but I have to study the client-remote thingy.

Have you checked out https://github.com/numToStr/FTerm.nvim?

gitui inside FTerm.nvim has been my preferred method to interact with git from within nvim. gitui has indeed proven to be a great frontend to git.

I did a bit of hunting and came across FTerm.nvim and I immediately notice that it is created and maintained by numToStr who also maintains Comment.nvim which is my preferred Neovim commenting plugin, which has always always worked great.

If you’re talking about the terminal inside a floating window, I think fterm.nvim is one which people commonly use.

I use https://github.com/numToStr/FTerm.nvim since you can specify in the setup which shell to use

It only work for very simple situation (project with only one build target), but it quite save a lot of time for me. For much complex situation, I prefer to write a singe bash script for specific project, and run them in FTerm