Neovim interprets a built-in colorscheme differently when the same file is used in my user directory.
nvim (and vim) both ship with a built-in colorscheme named delek.
/usr/local/share/nvim/runtime/colors/delek.vim (an unmodified file from the nvim installation) to my local directory:
~/.config/nvim/colors/delek_local.vim and changed only the name of the file and the name of the colorscheme inside that file:
let g:colors_name = "delek_local"
I then run nvim with no configuration:
% nvim -u NORC
and create a very basic python file like below just to see some highlighting:
Next enable syntax highlighting:
Next set the colorscheme to the built-in delek:
I see a color change at this point, which is expected.
Next set the colorscheme to the local copy, delek_local:
The colors change!
This doesn't make any sense to me. It's literally the same exact colorscheme file copied from location a to location b with only a name change. I get the same behavior when copying other built-in color files locally, and the unexpected results are different from each other, so its not as simple as nvim is not recognizing the local files and falling back on some default.
Can anyone explain this behavior? I'm struggling to get consistent colorschemes across different platforms and ran into this.