flatten.nvim VS nvim-unception

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.

I don't. I use a terminal, and https://github.com/willothy/flatten.nvim

You can also use the built-in terminal and use any terminal file manager you want. nvim-unception or flatten.nvim can be used to prevent nesting.

Check out flatten.nvim! (shameless self-promo but it stops nested instances from opening)

Here is the link to the issue: https://github.com/willothy/flatten.nvim/issues/19

You can also use the built-in terminal and use any terminal file manager you want. nvim-unception or flatten.nvim can be used to prevent nesting.

Flatten was inspired by nvim-unception, which accomplishes the same goal but can be difficult to configure in my opinion.

I’d look at how https://github.com/samjwill/nvim-unception does it.

This is my plugin. The relevant use case is demoed here from 30 seconds onwards. Basically, I block a terminal buffer forever until the git commit message buffer is BufUnloaded, which triggers an autocmd that unblocks the terminal buffer. However, it currently only works by opening the git commit message buffer in a new tab.

Try unception

I wrote nvim-unception and posted about it several months back; some people seemed to like it, even though it was still a bit rough around the edges.

I'm obviously incredibly biased, but since I prefer to use the built-in terminal emulator instead of Tmux for multiplexing and running quick bash commands, the biggest improvement for me personally was implementing a plugin that I wrote to quickly open files from inside the terminal buffer, and a keybind that I made to open a terminal window in the directory of the file that has focus.

U could use a plug plugin like nvim-unception to do what you are trying to do more efficiently.