Opening neoterm creates a blank buffer

[bronzehedwick]

Using Topen or Ttoggle creates a blank [No Name] buffer, which clog up the ls list. Minor, but annoying.

[kassio]

Hi @bronzehedwick! I wasn't able to replicate what you're saying with the following minimal init.vim:

set runtimepath-=~/.config/nvim
set runtimepath-=~/.config/nvim/after
set runtimepath+=~/.config/nvim/pack/minpac/start/neoterm " your neoterm path here.
set inccommand=split

Can you try it with a minimal init.vim like that and if the problem persists tell me please:

• neovim version
• neoterm version
• what termianl you're using
• what OS

[bronzehedwick]

Hm, I wasn't able to replicate on the provided minimal config either. I should have thought of doing that before creating the issue. Sorry about that.

I'll play some plugin whack-a-mole and see what's causing the issue.

[kassio]

Cool, I'll close it for now, but feel free to re-open it if you find something.

[bronzehedwick]

I finally got some time to research this, and this issue happens when set hidden is also active.

[kassio]

do you have a miminal vimrc for tests, please?

[bronzehedwick]

Yes, here's the minimal vimrc I used to recreate the issue:

set runtimepath-=~/.config/nvim
set runtimepath-=~/.config/nvim/after
set runtimepath+=~/.config/nvim/plugged/neoterm
set inccommand=split
set hidden

[kassio]

Even with the given minimal init.vim I wasn't able to replicate it:

[bronzehedwick]

Interesting. I was able to replicate the issue after calling Topen, then Tclose twice. Strangely, the first times I call Topen and Tclose I don't get the extra buffers, but every subsequent time I do.

[kassio]

wow! yeah, I was able to replicate it, this is a huge problem actually!

🏃 I'll investigate it ASAP!

[bronzehedwick]

:+1: