onivim / oni

Oni: Modern Modal Editing - powered by Neovim
https://www.onivim.io
MIT License
11.35k stars 299 forks source link

Broken cursor and current line highligting after CtrlSpace #401

Closed unclechu closed 7 years ago

unclechu commented 7 years ago

When I enter CtrlSpace window and close it I have my cursor looking as in insert-mode and current line isn't highlighted until I go to different mode and then back, or for example press % (move around brackets).

Minimal init.vim to reproduce it:

filetype off
exec 'set rtp+='. ($HOME) .'/.config/nvim/bundle/Vundle.vim'                                                                                             
call vundle#begin($HOME . '/.config/nvim/bundle')                                                                                                        
Plugin 'gmarik/Vundle.vim', {'pinned': 1} " provided by git-submodule                                                                                    
Plugin 'vim-ctrlspace/vim-ctrlspace'                                                                                                                                
call vundle#end()                                                                                                                                        
filetype plugin indent on 
set hidden

Short screencast that demonstrates the issue: https://youtu.be/UgTj4i49T5Y

I'm sure it isn't connected directly to the CtrlSpace plugin but the Oni's issue, it was just obvious way for me to reproduce it. In nvim TUI or nvim-qt GUI it can't be reproduced.

keforbes commented 7 years ago

This is probably related to #331.

bryphe commented 7 years ago

Yep, seems like the same issue as #331 - just a different manifestation of it. Thanks for including the video, @unclechu , that's very helpful.

unclechu commented 7 years ago

I built Neovim 0.2.0 release (without updating Oni) and now current line is highlighted after I leave CtrlSpace window but cursor is still thin line in normal-mode until I reset it.

bryphe commented 7 years ago

This should be addressed by #530 - please reopen if that fix does not address this.