C.D. MacEachern
C.D. MacEachern
Ok, even weirder and maybe a Vim bug: if seems as long as 'termguicolors' is not set, even if you're running GUI, the ANSI colors defined by this guard aren't...
Stranger yet, using latest MacVim, and explicitly starting a terminal like so: ``` call term_start('/usr/local/bin/bash', { 'ansi_colors': ['#1c1c1c', '#af5f5f', '#5f875f', '#87875f', '#5f87af', '#5f5f87', '#5f8787', '#6c6c6c', '#444444', '#ff8700', '#87af87', '#ffffaf', '#87afd7',...
More investigation (I have a strange idea of fun...). When remove ~/.vim/gvimrc from the equation to rule that out and keep my ~/.vim/vimrc with `colorscheme apprentice` and termguicolors are off,...
The fix, for MacVim (maybe other GUIs?) is to explicitly set the `Terminal` highlight bg color. I've just done: ``` augroup Vimrc autocmd ColorScheme apprentice hi! Terminal guibg=#262626 augroup END...
Could there be a workaround to check if the OptionSet was fired as result of last command being the sourcing of a Vim filetype buffer?
Yeah, I'm not sure there's a foolproof way to do it. For now, I'm just going to stick a call my `:nohlsearch` binding manually after I save my `vimrc`: `autocmd...
> 3. Do not assume terminal has black background (define `Normal` colors) I'd reword that as "Always be explicit," two of the bugs I've reported now have been because something...
I'd love to help out here - I've filed and helped fix bugs with the revamp of the colorschemes over at vim/colorschemes. I think @justinmk is on the right track...
Still happens on neovim HEAD 0.8.0-dev-917-gbaaaa1f2b, the README.md should include `use { 'wbthomason/packer.nvim' }` in order to work without error. I think it's because if you have no packages defined...