weirdly, this happens with sudoedit in alacritty, but doesn't happen with normal nvim command in alacritty, nor with either sudoedit or nvim in xterm. So there are two preconditions that must be met for this to happen: alacritty and sudoedit.
When this happens, syntax and UI colors are different from what they should be. All fg seems to be on grayscale. Line numbers are black, most code text is white, except comments which are grey. Visual selection makes bg black; the only non-grayscale color seems to be the default terminal background (*.background: #132738).
Error message on starting nvim:
Error detected while processing function <SNR>15_X:
line 8:
E421: Color name or number not recognized: ctermfg=FF9A00 ctermbg=NONE
E421: Color name or number not recognized: ctermfg=FF9A00 ctermbg=NONE
title.
weirdly, this happens with sudoedit in alacritty, but doesn't happen with normal
nvimcommand in alacritty, nor with eithersudoeditornvimin xterm. So there are two preconditions that must be met for this to happen: alacritty and sudoedit.When this happens, syntax and UI colors are different from what they should be. All fg seems to be on grayscale. Line numbers are black, most code text is white, except comments which are grey. Visual selection makes bg black; the only non-grayscale color seems to be the default terminal background (
*.background: #132738).Error message on starting nvim:
scriptnames output:
15: ~/.local/share/nvim/plugged/cobalt2-vim-theme/colors/cobalt2.vim