Yatao Li
I have opposite scenarios where termguicolors breaks highlighting. A GUI is not a TUI so I think by definition, termguicolors should be irrelevant, because what it does is to force...
I think it's because the colorscheme you're using is broken in notermguicolors?
I remember earlier (back when I haven't started the FVim project) that some colorschemes will use aggressive approximations when termguicolors is detected.
On my current colorschemes ( `let s:vsim_theme_name = ['falcon', 'gruvbox', 'gruvbox', 'Tomorrow', 'Tomorrow-Night', 'Tomorrow-Night-Blue', 'pencil', 'pencil', 'colorzone', 'PaperColor', 'PaperColor']` ), setting {no,termguicolors} doesn't affect anything
@jdhao could this be related: https://github.com/equalsraf/neovim-qt/issues/219
I've experienced incorrect color settings in `falcon` because it has `has('gui_running')` and in fvim it's always 0 So if in a colorscheme file: ``` if !has('gui_running') "do something with termguicolor...
Yeah. I'd rather want `has('gui_running')` to be fixed instead of setting `termguicolors`. Nevertheless, the current behavior is wrong. FVim reports neither a GUI, nor a terminal capable of showing GUI...
Harfbuzz font name problem. Can you upload the custom build? I'll take a look to see what Harfbuzz thinks the name really is.
You mean, a single ttf file now represents two fonts?
Let me grab 3.0 now..