kylo252

> Is there a way to check if you have these dependencies? @owod24, try this 1. check for neovim's clients `:checkhealth provider` 2. check telescope's dependencies `:checkhealth telescope` 3. [optional]...

> Finally getting around to finishing this up We should implement this fail-safe as well: https://github.com/LunarVim/LunarVim/pull/2093#issuecomment-1000167885

> The only real way I can think to get around this is to make `rolling` the legacy rolling branch and `rolling-0.6` the new rolling release branch for Neovim 0.6....

> I would agree, but we cannot do this for old versions that expect `rolling` or `master` to be the branch. That's the primary reason I suggested it in the...

> Suppose they decide to update a month after the fail-safe is introduced but they are using version 0.5. `:LvimUpdate` will simply pull from `rolling` without checking and without the...

> That's unfortunate, by "this" do you mean "lvim --update" or just running the init as normal? This code is marked as draft for a reason, I've not pushed any...

> I don't think completely splitting it off is the right choice, how about something like this? Yeah, that was my intent as well, just call another script to handle...

Reminder: if we're doing the plugins' version uplift in headless, then we need to log all their "breaking" changes. Just use whatever packer is using, hopefully it's logging those already.

Please try disabling autopairs for the filetype that you're testing.

1. Do you have Neovim >= 0.6? 2. Can you run AppImages? 3. Do you have recent `gcc` and `libc`? ```shell gcc --version # should be 4.8+ ls /usr/lib/libc-2*.so #...