Open mhdna opened 1 year ago
This occurs because of a bug in neovim https://github.com/neovim/neovim/issues/22263
I've added a mitigation so lualine doesn't trigger this bug. https://github.com/nvim-lualine/lualine.nvim/commit/2ac8d77575926d5c22f1d13f3e48000d579277e3
For now, lualine no longer schedules the ModeChanged events for operating pending mode. But this also means lualine no longer refreshes when user enters op-pending mode. But at least you should no longer hit 100% CPU uses when you enter op-pending mode.
@shadmansaleh Thanks for the quick mitigation.
Hopefully the nvim team gets this resolved soon.
Hi again,
Now that the https://github.com/neovim/neovim/issues/22263 issue got resolved, isn't it time to remove this temporary mitigation so that lualine refreshes properly when it enters O-PENDING mode?
Self Checks
How to reproduce the problem
In normal mode, press any pending operator (e.g.
d
,c
, ory
) without pressing the waiting movement command (i.e. pressd
withoutj
for example).Expected behaviour
Normal cpu usage.
Actual behaviour
Neovim is the top cpu consumer.
Minimal config to reproduce the issue
require('lualine').setup()