lazygit.nvim VS neovim-remote

There is even a plugin for Vim, that lets you open it in a floating overlay. https://github.com/kdheepak/lazygit.nvim

there's a lazygit plugin if you want to skip the step of opening Toggleterm

I really like this lazygit integration: https://github.com/kdheepak/lazygit.nvim

So I use https://github.com/kdheepak/lazygit.nvim All of my git workflow is done in lazygit gg opens the float and away I go

I don't use IntelliJ, so, I don't know how it exactly looks like. But I use this: https://github.com/kdheepak/lazygit.nvim

Why not just use lazygit.nvim?

But using vim-floaterm instead of the https://github.com/kdheepak/lazygit.nvim plugin (which mentions a different plugin https://github.com/akinsho/nvim-toggleterm.lua#custom-terminals as an alternative).

Have you heard of lazygit.nvim?

There is also Neovim plugin which can open lazygit in a floating window. Files will be opened in the active Neovim instance.

https://github.com/kdheepak/lazygit.nvim

Notice that this script depends on mhinz/neovim-remote: Support for --remote and friends. (github.com). (nvr as you have notice). The full-path is required to make it work.

I am currently using https://github.com/mhinz/neovim-remote with this bit in my zshrc:

Since they are on different screens I cannot use a single neovim instance (I tried playing around with neovim-remote but seems like that's for the usecase of opening files in one instance from different terminals -- doesn't help). Due to multiple LSP instances changes in one file are not reflected in the other, e.g., file B imports some types from file A; I create a new type in A but since B's neovim instance is not aware of any change to the A file corresponding the LSP fails to see the new type.

This version includes `nv` binary which is [neovim-remote](https://github.com/mhinz/neovim-remote) but rewritten in Rust (I've did it out of boredom) also with interface similar to `page`.

Practical use case: when navigating in ANY terminal (or tmux) write a function that sends opened files to a single running neovim instance instead of spreading opened vim instances all around like neovim remote does, but works for any terminal

I see the integration with neovim is done via a separate plugin, did you think about adding support for neovim-remote?

Another way of doing what u/TheLeoP23 suggested is by using https://github.com/mhinz/neovim-remote . This way you have a single neovim instance and you can open it on different terminals and mantain your current workflow.