diff options
author | Oliver Marriott <rktjmp@users.noreply.github.com> | 2022-06-19 01:33:58 +1000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-06-18 08:33:58 -0700 |
commit | 1ad6423f02bad6d7941ca38f2d5f7b757811e022 (patch) | |
tree | 4d431afd2e7d3cba853827622fad5f1103c49bd5 /src/nvim/api/vim.c | |
parent | 901fde60c6a4679648e9c0bd714a0c6dac97fe31 (diff) | |
download | rneovim-1ad6423f02bad6d7941ca38f2d5f7b757811e022.tar.gz rneovim-1ad6423f02bad6d7941ca38f2d5f7b757811e022.tar.bz2 rneovim-1ad6423f02bad6d7941ca38f2d5f7b757811e022.zip |
fix(highlight): use ctermbg/fg instead of bg/fg when use_rgb=false #18982
If `use_rgb` was false, we would attempt to set the `cterm_bg_color` to the
variable `bg`, which is only retrieved from `bg` and `background` keys, not
`ctermbg`. Same for `fg`. This means the values would be `-1` (the default,
un-got value) and we'd always set the returned values to `0`.
My understanding is `fg/bg` is always "gui" values, so instead we should be
using `ctermbg` when needed.
Nb: when looking around I think this function is currently *always* called with
`use_rgb = true`.
Diffstat (limited to 'src/nvim/api/vim.c')
0 files changed, 0 insertions, 0 deletions