Open hakamadare opened 2 years ago
@qvacua this problem still exists in VimR 0.36.0 (20220102.161018)
Same problem here. I was using lang en_US.UTF-8
to get unicode clipboard to work (#880) and in 0.36 it stopped working.
@qvacua i tested again with VimR 0.42.0, since i saw in the release notes that you had re-added libintl
; i still see the behavior i described in this ticket.
it looks like the NvimServer
on my system isn't linked against libintl
:
$ otool -L /Applications/VimR.app/Contents/Resources/NvimView_NvimView.bundle/Contents/Resources/NvimServer
/Applications/VimR.app/Contents/Resources/NvimView_NvimView.bundle/Contents/Resources/NvimServer:
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 1141.1.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
/usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
is it statically linked?
have you been able to replicate the issue? do you agree that it is an issue? 😁
Same thing for me in VimR 0.42.0. I don't use SpaceVim. Is there a quick way to trace where the error comes from?
Ah found it. Just the language messages
command
@huyz i just tested against VimR 0.44.0, and i can no longer replicate it 🥳 thank you @qvacua!
I haven't seen this error in ages either.
After upgrading to VimR 0.35.0 (20211105.213803), I see the following error when launching VimR:
I've traced the error message to my installation of SpaceVim (https://github.com/SpaceVim/SpaceVim), specifically this line:
https://github.com/SpaceVim/SpaceVim/blob/5c63ce1fec7fa70aba51961f720c4d403f85c649/autoload/SpaceVim.vim#L1399
This error message only appears when I use the embedded neovim in VimR, and I can replicate it. Here's the embedded neovim from VimR:
And here is neovim 0.5.1 installed via Homebrew, running in a terminal:
No error message in the second case.
Finally, when I roll back to VimR 0.34.0-355, I no longer see the problem: