New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange error when closing Codi on NeoVim / OS X #45
Comments
Can you provide more context and logs? e.g. how did you start vim, any keystrokes to reproduce the issue, whether or not this happens with a minimal vimrc, etc. |
Here are the logs:
I'm using Codi with the following mappings: nnoremap <C-A-n> :Codi javascript<CR>
nnoremap <C-A-p> :Codi python<CR>
nnoremap <C-A-l> :Codi lua<CR>
nnoremap <C-A-\> :execute 'silent! Codi!'<CR> The error occurs when opening Codi and then closing it directly after using something like The following init.vim causes it as well. nnoremap <C-A-n> :Codi javascript<CR>
nnoremap <C-A-p> :Codi python<CR>
nnoremap <C-A-l> :Codi lua<CR>
nnoremap <C-A-\> :execute 'silent! Codi!'<CR> |
Can't reproduce this. Does this also happen with vim instead of nvim? I'm baffled as to why this could be happening; the lo g line |
It does, but it requires significantly faster keypresses to do it (i.e. basically at the same time). Could just be some sort of race condition with neovim having a different plugins structure? Pure vim 7.4 .vimrc: call plug#begin('~/.vim/plugged')
Plug 'metakirby5/codi.vim'
call plug#end()
nnoremap <C-n> :Codi javascript<CR>
nnoremap <C-p> :Codi python<CR>
nnoremap <C-l> :Codi lua<CR>
nnoremap <C-\> :execute 'silent! Codi!'<CR>
let g:codi#log= '/tmp/codi.log' And logs:
This may or may not be fixable on your end. In NVim this happens pretty frequently but considerably less in ViM (it may not even be the same error but I have no idea how to read the codi logs to tell). |
On OS/X El Capitan using NeoVim v0.1.3-350-gc94575f, I get the following error when using
Codi!
:Codi still seems to work fine but it forces me to hit Enter before I can do anything else again and for whatever reason
silent!
doesn't seem to fix it.The text was updated successfully, but these errors were encountered: