Closed janlazo closed 4 years ago
I'm unable to reproduce this.
Minimal configuration:
if has('nvim')
set runtimepath^=~/.vim runtimepath+=~/.vim/after
let &packpath = &runtimepath
endif
call plug#begin('~/.cache/vim/plugins')
Plug 'junegunn/fzf'
Plug 'junegunn/fzf.vim'
Plug 'sainnhe/edge', { 'as': 'vim-color-edge' }
call plug#end()
set termguicolors
set background=light
augroup testFzf
autocmd!
autocmd ColorScheme * unlet g:fzf_colors
augroup END
colorscheme edge
Demo:
I think this is visible enough, please provide steps to reproduce it.
In addition, why do you want to unlet g:fzf_colors
? This color scheme is optimized specifically for fzf.
neovim-qt, nvim 0.5.0, Ubuntu 16.04
GVim, Vim 8.2 Windows 10 (Edge VM). I can't replicate the invisible text on the VM. I saw it on my Windows work machine only so I'll add the screenshot if needed next week.
I don't want to unlet g:fzf_colors
but I don't know how else to avoid it. Perhaps set g:fzf_colors
only if not running on Windows.
nvim-qt, nvim 0.5.0, Windows 10 (Edge VM). I reproduced here.
I'll mitigate the text,background color issue in upstream instead.
g:fzf_colors is okay in dark background.
Tested with fzf.vim, GFiles command, termguicolors on, light background.
Workaround is to use an autocmd to
unlet g:fzf_colors
after setting the colorscheme.