Justin M. Keyes wrote: > 2018-03-24 8:41 GMT+01:00 Christian Brabandt <[email protected]>: > > While I am sympathetic with keeping in sync with the Neovim change, I don't > > think setting internal Vim variables is a good way to specify the color. > > Isn't it better to have some kind of option or perhaps use a highlighting > > group to set those colors? That comes with the advantage that the user can > > enter :verbose ... and check where that was actually set, while simply > > setting a variable leaves no clue which script set those. > > > > The global variables are a hack, I suggest instead highlight group > names like TermColor1, TermColor2, for each of the color indices. > > Example: > > :hi TermColor4 guifg=lightblue ctermfg=lightblue
Hmm, although this could be made to work, there are some conceptual differences between a highlight group and the ANSI colors of a terminal. Highlight groups are meant to be global, specify the colors of some language or status line elements. The colors of the terminal might depend on what's running in that terminal. And a highlight group provides attributes, which would not apply here. -- hundred-and-one symptoms of being an internet addict: 50. The last girl you picked up was only a jpeg. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
