Unsetting custom nvim binary does not work

[p3palazzo]

Unsetting custom nvim binary does not work

[georgeharker]

I’ll take a look at the alert side.

[qvacua]

@p3palazzo : My guess is that I cannot reproduce it due to a subtle difference between macOS versions; I'm on Sonoma. If my guess is right, the new snapshot above should fix the issue: Please try it.

[georgeharker]

Thanks for the report. That should be throwing up an alert saying incompatible version (upstream fixes were needed for this to work which are in newer versions) can you let me know if that alert shows. We will look at why unsettling doesn’t work.

[zornme]

I am having the same issue and wanted to chime in to say that the alert does not show. VimR hangs at load and then after a few seconds displays the blank screen. I've attached a screenshot as well. Thank you for all of your work on this project.

[p3palazzo]

Exactly, that's my experience, too. No alert and just the blank window after a few seconds at startup.

[qvacua]

I'm afraid, I cannot reproduce the issue. I'm not sure, but, I made a small change which might fix the issue. Can you please try https://github.com/qvacua/vimr/releases/tag/snapshot%2F20231129.173509 ?

[qvacua]

BTW: @p3palazzo : Which version of macOS are you using?

[p3palazzo]

Ventura with the latest updates applied.

[p3palazzo]

Now it clears the path to the incompatible nvim binary on quit and relaunch, which solves the blank window problem, but still doesn't throw any alert.

[georgeharker]

I have some fixes for getting an incompatible version alert to show (it's a bit complex as older neovim without the upstream fix we submitted will block io until a connection is made on stdin, but we should have something soon.

[qvacua]

https://github.com/qvacua/vimr/releases/tag/v0.45.1-20231211.195158 contains the fix.