SNAPSHOT-20231110.205939

[qvacua]

• VimR is not using custom build binary using libnvim anymore. Thanks to Remove uibridge, allow basically unmodified nvim binary #1015 by georgeharker, VimR now even can use external Neovim binary.
• Neovim 0.10.0-dev
• Minimum macOS requirement is now Ventura (v13).
• Fix VimRSetCharacterspacing: Fix VimRSetCharacterspacing #1014
• Add basic file handling to the filebrowser: Add basic file handling to the filebrowser #1005
• Provide neovim original commandline interface: feat: provide neovim original commandline interface #1003
• Add an option for custom Markdown processor: Custom markdown processor setting #745
• Dependencies updates:
  • ReactiveX/RxSwift@6.6.0
  • sparkle-project/Sparkle@2.5.0
  • apple/swift-collections@1.0.5
  • Quick/Nimble@13.0.0

---

This discussion was created from the release SNAPSHOT-20231110.205939.

[wookayin]

Congratulations and great work @qvacua and @georgeharker.

VimR now even can use external Neovim binary.

One question -- How is this possible? Also, if using an external neovim, would has("gui_vimr") still return 1?

[georgeharker]

Currently that isn’t set. But will work on something like it. The has(‘gui_running’) will work.

[georgeharker]

I should note g:gui_VimR will be set.

This works by using messagepack api to Neovim.

As such because neovim wasn't compiled with a gui in has(gui) reports false. But has(gui_running) will be true as well as g:gui_vimr being 1.

Tidying up this is a work I. Progress. I'm not sure if new options can be created with an external neovim.