There are two [No Name] buffer on the start

[nyngwang]

As title. I use nvim . to start neovim from the current directory. It seems that this has been mentioned by people before but I forgot the keyword(s) to find the issue.

[cseickel]

I don't think those are from neo-tree. When I open with nvim . I end up with a single buffer named:

neo-tree filesystem [1000]

[nyngwang]

@cseickel: You might want to take a look. To make it clear, I stop the recording at the last moment when the content of neo-tree floating window was about to be shown. These three buffers are:

1. current working directory as CWD/. This one will disappear after the content of neo-tree gets shown.
2. [No Name]
3. [No Name]

And I assume this is related to neo-tree because this didn't happen some months before, and I didn't install any other file-tree-related plugins.

demo.mov

[cseickel]

I think those extra buffers being displayed are the result of whatever tabline plugin you are using being out of sync. Run the :ls command to see if those buffers really exist. If you have neo-tree opening as a sidebar, then there should be exactly one [No Name] buffer when it finishes the netrw hijack.

[nyngwang]

@cseickel:

I got this:

[...] whatever tabline plugin you are using being out of sync. [...]

OK, this is possible. I'm using https://github.com/akinsho/bufferline.nvim, but I don't know how to check it. Do you also use this plugin?

[cseickel]

If it is showing the extra [No Name] with :ls then they are really there and it's probably not a problem with bufferline at all. I would still think it is a conflict with another plugin though.

[cseickel]

Actually, I take it back. I get the same thing when I change the default position to "float". I'll take a look.

[nyngwang]

@cseickel: Really thank you! If you're busy with the other things it's OK to fix this after them, since I just made a little hot-fix for it.

[nyngwang]

I suspect that this would cause a related problem in integrating with fzf-lua(ibhagwan/fzf-lua#390). But it's also possible that this is related to the bufferline.nvim plugin.

The explanation for the following demo: If I change it from float to right then the buffer did get "shown", but the buffer is not listed, so there are only two [No Name] buffers in the demo:

debug_2.mov

Current workaround:

vim.keymap.set('n', ';', function ()
  if vim.bo.filetype ~= 'neo-tree' then
    vim.cmd('NeoNoNameClean') -- This will merge those `[No Name]` buffers into a single one
  end
  vim.cmd('Neotree float toggle reveal_force_cwd dir=' .. vim.fn.getcwd())
  if vim.bo.filetype ~= 'neo-tree'
    and not vim.api.nvim_buf_get_option(0, 'buflisted') then
      vim.cmd('set buflisted') -- This will set the current buffer the one selected by fzf-lua.
  end
end, NOREF_NOERR_TRUNC)

[nyngwang]

@cseickel: Could you prioritize the fix of this issue? I assume the fix would be not that complicated. I encountered many little bugs related to this when interacting with some other plugins. Sorry for being hurry.

[cseickel]

@nyngwang I think this is fixed in main, give it a try and let me know if it is working for you.

[nyngwang]

@cseickel: Perfect! Let me close it now!