Closed coffebar closed 3 weeks ago
Came here to report the same. Commenting out the render.update()
call in the autocommand in events.lua
makes the error go away:
create_autocmd('DiagnosticChanged', {
callback = function(event)
state.update_diagnostics(event.buf)
-- render.update()
end,
group = augroup_render,
})
The error happens regardless of how I close a tab: :bd
or click the X in the tab.
Is barbar up to date? That file is different in master
Aha, yes it works on master. I had this in my config (so does @coffebar 's minimal example)
version = '^1.0.0', -- optional: only update when a new 1.x version is released
Ah, we've yet to create a new version with that. I'll add that to my to-do list.
Thank you for bringing this to my attention!
Yep, we need a release. Removing version = '^1.0.0',
tag helped for me, but this line is from readme instructions.
I've published a new release! Closing this, but let me know if there are further issues.
Description Constantly see
E315: ml_get: Invalid lnum
error when switch projects (plugins close some buffers) on latest neovim (build neovim from git master branch).Found steps to reproduce this message with minimal config:
But when I use my personal config, I see only this message:
disabling barbar.nvim removes this message
To Reproduce
init.lua:
Steps to reproduce the behavior:
nvim -u /tmp/barbar/init.lua /tmp/barbar/init.lua
Informations Neovim version: v0.11.0