Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing multiple buffer issues. #919

Closed
wants to merge 4 commits into from
Closed

Conversation

sherocktong
Copy link

No description provided.

@sherocktong
Copy link
Author

To fix the error below:

E5108: Error executing lua ...nvim/lazy/bufferline.nvim/lua/bufferline/diagnostics.lua:72: attempt to call field 'enabled' (a nil value)
stack traceback:
	...nvim/lazy/bufferline.nvim/lua/bufferline/diagnostics.lua:72: in function 'diagnostic_is_enabled'
	...nvim/lazy/bufferline.nvim/lua/bufferline/diagnostics.lua:84: in function <...nvim/lazy/bufferline.nvim/lua/bufferline/diagnostics.lua:80>
	...nvim/lazy/bufferline.nvim/lua/bufferline/diagnostics.lua:148: in function 'get'
	...are/nvim/lazy/bufferline.nvim/lua/bufferline/buffers.lua:63: in function 'get_components'
	...local/share/nvim/lazy/bufferline.nvim/lua/bufferline.lua:56: in function <...local/share/nvim/lazy/bufferline.nvim/lua/bufferline.lua:54>

It was encountered when neovim version is 0.10

@sherocktong sherocktong changed the title Pr Fixing multiple buffer issues. Jun 6, 2024
@akinsho
Copy link
Owner

akinsho commented Jun 7, 2024

This error seems strange if a user has v0.10.0 which I'm on they should have this method available. I just tested this locally and don't experience this error. Can you please every part of your installation is working correctly and you are definitely on the correct version. You can also verify the behaviour by printing out the contents of vim.diagnostic to ensure that it is actually present

@PeiweiHu
Copy link

I met the same error on:

➜   nvim --version
NVIM v0.10.0-dev-847+gc0ac53e0d
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Run "nvim -V1 -v" for more info

@akinsho
Copy link
Owner

akinsho commented Jul 18, 2024

Closing due to inactivity please comment back here in response to my earlier comment to resume discussion

@akinsho akinsho closed this Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants