[Bug]: (UNKNOWN PLUGIN): Error executing lua: attempt to call a number value about bufferline.nvim HOT 5 OPEN

The problem only occurs when you open nvim using the directory reference in question Ex: nvim .

The bug did not occur when calling only nvim in the directory in question.

My config

require("bufferline").setup
{
  options = 
   {
      mode = "buffers",
      close_icon = '',
      separetor_style = 'thin',
      offsets =
      {
	{
           filetype = "NvimTree",
           text = "File Explorer",
	   highlight = "Directory",
	   separetor = true,
           padding = 1
	},
      },
    }
  }

from bufferline.nvim.

UPDATE:

It seems that this plugin works with Tokyonight's v2.9.0 version, but not v3.0.0 or v3.1.0. The issue can still be observed in v2.9.0, all the way back to the initial v1.0.0 release.

UPDATE:

I tested multiple versions for each of bufferline, tokyonight, and nvim-treesitter, going back to their respective initial releases while keeping the other two plugins at their most recent versions. Furthermore, I tried simultaneously decreasing the versions of all three plugins, choosing versions for each that were released around approximately the same time, going back to late 2022.

For all combinations I tried, I was unable to find any where the error could not be observed.

from bufferline.nvim.

@pwnalone thanks for digging in and taking the time to document this issue. As you say I've never encountered this as I don't use Tokyo night and never have so it's not immediately clear what this interaction is. One possible cause could be how that plugin interacts with this. I think there might be some module of this plugin's that that theme is using that this plugin might not be expecting or it's interacting in some way.

Tbh I'm not likely to be able to dig into this anytime soon, anyone else who wants to take a stab should please do or just document more stuff in here. As always community contributions re a fix would be massively appreciated as I'm definitely not in a place where I can dedicate much free time to these issue.

from bufferline.nvim.

@akinsho Thanks for getting back to me so quickly on this. I have switched to a different colorscheme as a temporary fix, but will try to troubleshoot this issue some more if I find the time. If I discover the source of the issue, I'll open a PR. In any case, I'll keep documenting any relevant information here.

from bufferline.nvim.

I am also experiencing this issue. I am using sainnhe/sonokai if that's helpful but I was able to produce it with nvim's default colorscheme.

At one point I thought it was folke/todo-comments.nvim because after adding event='VimEnter' I was able to avoid the error. I made a bug there but wasn't able to produce it using only todo-comments so I closed it. folke/todo-comments.nvim#254

Here is a bare bones version of my init.lua that will also produce the error.

local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "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", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  {
    "nvim-tree/nvim-tree.lua",
    config = true,
    dependencies = { "nvim-tree/nvim-web-devicons" }
  },
  {
    'akinsho/bufferline.nvim',
    config = true,
    version = "*",
    dependencies = 'nvim-tree/nvim-web-devicons',
  },
  'neovim/nvim-lspconfig',
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

from bufferline.nvim.