Simon

Regarding the delay merging the PR, the README says: > Kickstart.nvim targets only the latest ['stable'](https://github.com/neovim/neovim/releases/tag/stable) and latest ['nightly'](https://github.com/neovim/neovim/releases/tag/nightly) of Neovim. So it would make sense to merge this now...

Call me the PR necromancer :sweat_smile:

@t-wissmann what is the current state of this? Should somebody take over? We also discussed that maybe removing ancient gcc support (seeing that we first should fix brand [new gcc](https://github.com/herbstluftwm/herbstluftwm/issues/1612)...

Had a look around in the code today and in the commit https://github.com/folke/which-key.nvim/commit/6b023b4c29ecc0aad06a51dd14bd2754b43bb0c8, fixing an issue with macros and which-key, it looks like an "infinite recursion", or busy waiting loop...

According to https://github.com/LazyVim/LazyVim/issues/4553 folke is on vacation until the end of the month :palm_tree:

[Obligatory XKCD](https://xkcd.com/1172/) :sweat_smile: But seriously, is this `M.schedule()` loop actually needed? I tried the plugin without that line, or rather just a `return` and I could record macros without high...

Awesome, thank you! :rocket: