opens blank empty buffer in parent Nvim

[justinmk]

nvim in a :terminal opens the blank empty buffer in the parent. That's probably not useful, I would expect it to just ignore that case.

Should it only open actual, existing files in the parent?

[brianhuster]

It is useful because you can close that Nvim instance (which is likely just opened by mistake) by running :q on the non-nested Nvim, instead of having go to the nested Nvim and run :q inside it

[justinmk]

Hmm. Sometimes I test stuff in a nested nvim.

What are you thoughts on other non-file buffers? For example, echo foo | nvim opens a blank buffer in the parent, but "foo" contents in the nested nvim.

[brianhuster]

I think this snippet should work to prevent unnesting when you run nvim in :terminal

if vim.env.NVIM and #vim.v.argv == 2 then
    vim.g.loaded_unnest = 1
end

Please try it (make sure to put it before vim.pack.add() call).

What are you thoughts on other non-file buffers?

Yes, probably some special buffers like terminal, quickfix should be handled

I'm not against supporting your request as a config option, but I need to choose the config convention first (whether to use setup() or vim.g, or even Lua _G?

[justinmk]

It is useful because you can close that Nvim instance (which is likely just opened by mistake) by running :q on the non-nested

I don't get why that's useful, but even if it is, it has some problems:

• changes written to the buffer aren't reflected in the :terminal nvim (and it's impossible to make this work)
• ZQ doesn't always work (sometimes it doesn't exit the :terminal child nvim)

That seems more confusing than useful.

but I need to choose the config convention first (whether to use setup() or vim.g, or even Lua _G?

i think we need something like this in core (current defaulttable doesn't do this):

vim.defaulttable(vim.g.foo) = {
  a = ...,
  b = ...,
}

idk why we never added that. it would have avoided all the setup() noise.