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

Repeated error message when change detection is enabled #91

Closed
benjamineskola opened this issue Dec 22, 2022 · 2 comments · Fixed by #76
Closed

Repeated error message when change detection is enabled #91

benjamineskola opened this issue Dec 22, 2022 · 2 comments · Fixed by #76
Labels
bug Something isn't working

Comments

@benjamineskola
Copy link

Describe the bug

Every few seconds from startup I get the following error message:

Error executing luv callback:
vim/_editor.lua:0: E5560: nvim_echo must not be called in a lua loop callback
stack traceback:
        [C]: in function 'nvim_echo'
        vim/_editor.lua: in function 'notify'
        ...s/ben/Library/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:198: in function 'notify'
        ...s/ben/Library/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:222: in function 'warn'
        ...Library/nvim/lazy/lazy.nvim/lua/lazy/manage/reloader.lua:68: in function <...Library/nvim/lazy/lazy.nvim/lua/lazy/manage/reloader.lua:35>

Which version of Neovim are you using?

NVIM v0.8.1
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by brew@Ventura-arm64.local

Features: +acl +iconv +tui
See ":help feature-compile"

To Reproduce
Make sure to read https://github.com/folke/lazy.nvim/wiki/Minimal-%60init.lua%60-to-Reproduce-an-Issue

Steps to reproduce the behavior:

This occurs with a neovim config that I modelled after the one linked in the readme (folke/dot). It is resolved by setting change_detection = { enabled = false }`, but obviously that is not ideal. My init.lua, lazy.lua, plugins.lua.

I will follow up with disabling plugins and enabling one by one to determine whether a specific plugin creates the issue.

@benjamineskola benjamineskola added the bug Something isn't working label Dec 22, 2022
@folke folke closed this as completed in 28f1511 Dec 22, 2022
@folke
Copy link
Owner

folke commented Dec 22, 2022

Fixed!

This was actually caused by lazy trying to show you a warning that you need to set mapleader BEFORE loading lazy. Otherwise your keymaps might break

@benjamineskola
Copy link
Author

Thanks for such a quick fix! Lazy.nvim seems great so far. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants