v0.45.0-20231122.130444

[qvacua]

• VimR is not using custom build binary based on libnvim anymore. Thanks to Remove uibridge, allow basically unmodified nvim binary #1015 by georgeharker, VimR now uses stock Neovim and can even use external Neovim binary (from v0.10.0 on).
• Neovim 0.10.0-dev which means Neovim itself may have some rough edges.
• 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 v0.45.0-20231122.130444.

[metalelf0]

Hi, I downloaded the latest nightly but I'm getting the error "is damaged and can’t be opened. You should move it to the Trash". Tried xattr -cr on the app file but opening it shows a stacktrace (let me know if you need it). I'm on an M1 Macbook Pro.

[metalelf0]

It's doing nothing. The app starts, but it still opens the same stacktrace and force closes.

[nmder]

Hmm. Did you try the latest nightly that was built few hours ago? It's working on mine (Intel).

[metalelf0]

I just tried and I have the same error. App is damaged. Maybe there's something wrong with M1 macs?

[georgeharker]

I’ll download the official release and take a look today.

[georgeharker]

The current build downloads and works fine for me (i'm on M1) - what OS version are you on?

[metalelf0]

I'm on Sonoma 14.1.1.

…

On Sat, Nov 25, 2023 at 12:20 AM George Harker ***@***.***> wrote: The current build downloads and works fine for me (i'm on M1) - what OS version are you on? — Reply to this email directly, view it on GitHub <#1019 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABAGR5NKZPMPMMS54VVR5TYGETTRAVCNFSM6AAAAAA7WE5WZOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMNRUGAZTE> . You are receiving this because you commented.Message ID: ***@***.***>

[georgeharker]

Oh same here. Would you be able to find the crash report in console and post it?

[metalelf0]

Sure. Here it is (for reference, this is after `xattr -cr /Applications/VimR.app`): https://gist.github.com/metalelf0/5257dea8a95bdce8a1568aaf8769d7ce

[georgeharker]

In system prefs for security do you see any marker indicating the option to trust the app?

I’m pretty confused as to why this is occurring. Which security setting for trusted developers etc do you have set?

[sheff3rd]

Hello. I recently updated to VimR 0.45 and after update FZF and vim-esearch works really slow for me. I'm working on very large project, but I did not have any issues with it prior. Now it hangs for solid 10 seconds when I open fzf, and vim-esearch hangs vim

this was not an issue before the update. I also tried to do :PlugUpdate but that didn't help

[sheff3rd]

I was forced to downgrade. Version 0.44 works wonders without any lag and this was getting unbearable

[georgeharker]

Have you tried with an external / different version of nvim? Does this only occur with a specific version of fzf?

[sheff3rd]

No, I haven't tried another versions of nvim
I'm currently using NVIM v0.9.1

As for the the version of fzf or vim-esearch, I did run :PlugUpdate when trying to fix the problem but that didn't help, so both plugins should be the latest version

I will try updating both nvim and vimr and will report back

[sheff3rd]

Sorry, I haven't had time to check other versions of nvim, but I've just installed the latest VimR release and it works like a charm. This is great! I love it 🎉