vimr: coc.nvim causes vimr to instantly close the window
With the following minimal .vimrc, where only coc.nvim is enabled via vim-plug, the VimR window is closed right after starting the app. It doesn’t crash, it still sits running in the dock, but when I click the app icon it shows for less than a second and is closed again.
call plug#begin('~/.vim/plugged')
Plug 'neoclide/coc.nvim', {'branch': 'release'}
call plug#end()
Is there any way at all to get VimR to give me anything like a log file?
I’m using Version 0.29.0-329 installed via brew on Catalina 10.15.1.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 19
- Comments: 16 (5 by maintainers)
Commits related to this issue
- GH-768 Do not force re-sign NvimServer When coc.nvim is installed, EXC_BAD_ACCESS (Code Signature Invalid) occurs and NvimServer crashes. We force re-signed NvimServer on Mojave because the notarizat... — committed to qvacua/vimr by qvacua 4 years ago
- GH-768 Update release notes — committed to qvacua/vimr by qvacua 4 years ago
I’m seeing this also, but only in .29 – .28 doesn’t have this same issue.
I could reproduce the issue (as described by @metalelf0). The problem was some code-signing issue. TBH, I don’t know why there was a problem and why it is fixed now by https://github.com/qvacua/vimr/commit/765f2c43d7c2396f64f85dd08565c045ed9dbeaf. Please try SNAPSHOT-334.
I did not know coc.nvim until now, but it’s awesome. I now must fix this bug… 😃
Edit: in latest snapshot
SNAPSHOT-332, the issue is different. The vimr window doesn’t close anymore right after loading, but it remains unresponsive. It seems to load the UI correctly, all text is rendered correctly, but no input either by keyboard or mouse actually cause any change. Vimr CPU usage is close to 100% and it doesn’t respond to cmd-q either - I have to kill -9 it.