-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
disappearing colors on resourcing vimrc in neovim #144
Comments
I cannot reproduce the bug with the following step. set nocompatible
filetype off
set rtp+=/path/to/lightline.vim
filetype plugin indent on
set laststatus=2 Open neovim with |
I'll try figuring out how to reproduce it. I'm not sure right now. |
@itchyny figured it out. It has to do with sourcing vimrc again. https://www.youtube.com/watch?v=y2H0-5H7JVo&feature=youtu.be I also tested with default vim-airline and it doesn't seem to affect them. |
Please paste the minimal vimrc (which is under 20 lines at most) to reproduce the bug. Otherwise I cannot investigate the reason what causes the bug or even I do not know this is a bug of lightline or of other plugin or of Vim itself. |
@itchyny were you able to watch the video? I'll post a vimrc soon just give me a few. |
Yes but I found no clue to reproduce. I close this issue because the issue report is less informative. |
@itchyny sorry I didn't post the vimrc but did you watch the video? |
Yes |
filetype off
set rtp+=/usr/local/etc/dotfiles/nvim/plugged/lightline.vim
set rtp+=/usr/local/etc/dotfiles/nvim/plugged/Apprentice
filetype plugin indent on
set laststatus=2
colorscheme apprentice It only happens if a colorscheme is set (I tried apprentice and solarized etc.) Steps to reproduce
|
I still cannot reproduce because I don't see what |
@itchyny in neovim, the |
I still cannot reproduce with the following steps.
Am I doing incorrectly? |
Ah, OK. It seems to be appeared on my environment. |
great. hopefully you can figure out whats going on. |
@itchyny forgot to reopen the issue, its still closed even though you could reproduce it. |
@itchyny any updates on this? its still closed even though you managed to reproduce. |
I don't want be bothered by the behaviour which occurs only in neovim, the editor which has different architecture of rendering compared to Vim. |
@itchyny in that case i'll take a stab and see if I can fix it. |
@itchyny it has to do with running |
I fixed it, i'll create a PR |
I'm having this issue on Vim 8 on OSX. Is it related? I saw that the PR changed a block that was in |
@Billy- Please create a new issue if there's some trouble with environment info, precise steps expected behavior and minimal vimrc if possible. |
I hope I'll be able to find the spare time to do that.. |
In neovim terminals this happens sometimes only in 'terminal' or 'insert' mode.
Here it is in the same buffer but in normal mode.
No clue what's wrong.
The text was updated successfully, but these errors were encountered: