> Even under X11, those colors are configurable.
----
But apparently not under Vim...on Windows...
> So, it's got the "correct" 0xADD8E6 that you want. But it's not used.
---
Yup -- I knew there was a problem.
Wouldn't have suspected a hard-coded one...
>
> Is there any reason not to use the $VIMRUNTIME/rgb.txt versions of
> those colors?
Don't ask me -- ask Bram!
It's vim that is making use of it during syntax markup, so it's not like
I could tell it to read rgb.txt and use the right version ... er, wait,
that's
exactly what vim's supposed to be able to do...but that's not working.
Um...yeah...so scratch idea of me telling vim what to use...if a program
has hardcoded constants like that...well -- what can ya do? It's not like
you can reason with hard coded values... they just 'are'...
like stones.
> If there's some inefficiency with reading that file, maybe it makes
> sense. Nonetheless, sending a patch to vim-dev to update the
> hard-coded values to match the included runtime/rgb.txt values.
---
Hopefully it would read the file at build time and not be stored
in the source, Not good to have data manually coded into the source --
causes all sorts of unexpected problems...*cough*...
Thanks for finding the root cause!
It wasn't me that broke it this time!!! Yey!!!..
--
You received this message from the "vim_use" 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
No comments:
Post a Comment