bug: Navigate to parent directory with C-o makes the buffer buflisted

[Terseus]

Did you check the docs and existing issues?

• [X] I have read the docs
• [X] I have searched the existing issues

Neovim version (nvim -v)

NVIM v0.9.5

Operating system/version

Archlinux

Describe the bug

When using <C-o> to navigate to the parent directory, the buffer have buflisted = true, which causes to show in buffer list, in tabline plugins, etc.

What is the severity of this bug?

minor (annoyance)

Steps To Reproduce

1. cd a && mkdir b
2. nvim -u repro.lua
3. :e .
4. set buflisted? will show nobuflisted
5. enter in directory b using <Enter>
6. set buflisted? will show nobuflisted
7. <C-o> to navigate to the parent directory.
8. set buflisted? will show buflisted

Expected Behavior

set buflisted? must show nobuflisted at all times in oil.nvim buffers.

Directory structure

a/b a/repro.lua

Repro

-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
              -- add any needed settings here
            })
        end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Did you check the bug with a clean config?

• [X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

[ivanjermakov]

I have this problem generally with vim/neovim. Is there an upstream issue in neovim repo where logic of enlisting nobuflisted buffers is discussed?

[stevearc]

I did discover that this behavior is present in both Neovim and Vim. I filed it upstream on the Vim repo https://github.com/vim/vim/issues/14223