Do you remember if your order came on the estimated delivery date or earlier ? <| sep |> The main features of these color schemes are 1 . They distinguish between changing which red red is and changing which syntax elements are red as opposed to green . By default , they keep the same color assignments as vim ' s default color scheme , but change the underlying colors to match a base 16 theme unlike the linked schemes , which change not only whichredredis , but also whichthingsarered . 2 . They give you configuration options to change the colors of various syntax elements in a pretty simple way . For instance , you can set gbase 16 coloroverrides ' Comment ' ' fggreen ', ' Identifier ' ' fgblue ', . and so on , to make a custom color assignment that differs from the vim defaults . Then , all base 16 color schemes in the repo will use those color assignments while tweaking the underlying colors . 3 . They set all the gterminalcolor variables , which makes neovim emulated terminals use the base 16 colors . This is especially useful if you ' re changing color schemes on the fly , i . e . if the outer terminal uses a dark color scheme , and nvim uses a light color scheme , and you want a term inside vim to use the inner light scheme instead of the outer dark one . It ' s also real nice when you ' re using a theme like redscreen at night , which makes all text be different shades of red these color schemes will make that color scheme carry over into terms . The first 2 points could be backported to the vim themes and I think that would be valuable I think that separating the color palette from the colortosyntaxelement assignments is the right direction to go with color schemes . The third is nvim specific , obviously .