Skip to content
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

E421: Color name or number not recognized: ctermfg=FF9A00 ctermbg=NONE #6

Open
sshilovsky opened this issue Jun 2, 2022 · 0 comments

Comments

@sshilovsky
Copy link

title.

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

scriptnames output:

15: ~/.local/share/nvim/plugged/cobalt2-vim-theme/colors/cobalt2.vim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant