Empty start buffer never close on it's onw (opening a file via mini.files or mini.pick) ?

[Gael-Lopes-Da-Silva]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

all of the above

Question

I don't know if it's an expected behavior or if it's a bug from my configuration. When I start neovim, I'm put in an empty buffer. If I open a file with the mini.files or with mini.pick it open the file in a new buffer. So in the end I need to manually close this buffer if I don't want to [b or ]b in it by accident. Is there something I didn't understand with the current buffer workflow ?

Side note: if in this empty buffer I do :e , it replace the empty buffer with a new buffer containing the file.

[echasnovski]

Yeah, this is a side effect of d1f7e95. It is not an issue in case of using some "dashboard" type of plugin (like 'mini.starter'), so was overlooked.
I'll take a look if this is feasible to adjust.

---

Do you mind sharing why you've closed this?

[Gael-Lopes-Da-Silva]

Ah, ok. I closed this discussions because I found this one (#1485) which at first I didn't understand. But after playing with the auto command, I understood and find it a good solution. So I thought it was a duplicate of this conversation.

[echasnovski]

Closing this in favor of tracking in #1596.