rjooske

joined 1 year ago
sorted by: new top controversial old
Avoid nesting neovim in c/[email protected]
[โ€“] [email protected] 3 points 1 year ago

Thanks for the detailed answer! (or your attempt at answering ๐Ÿ˜…) I never knew neovim worked like that and that I could control it from outside. Definitely keeping this in my toolbox

Avoid nesting neovim in c/[email protected]
[โ€“] [email protected] 4 points 1 year ago

That's not exactly what I want. If you run git commit in a terminal buffer for example, git opens a new instance of neovim inside the terminal buffer (assuming you've configured git to do so), which is what I'm trying to avoid. I want git here to open a new buffer inside the currently running neovim instance as a place to edit the commit message. Sure, I can use Fugitive instead, but that doesn't work for commands other than git

11
Avoid nesting neovim (lemmy.world)
 

Is there a way to avoid opening a nested neovim instance inside a terminal buffer and instead open it as a new buffer inside the already running instance? I'm thinking something like what Fugitive does, but more general and that works for any shell commands.