> Michael Wookey wrote:
> >> Hm... Maybe the console version checks the values of the guibg=
> guifg=
> >> settings even though it doesn't use them. Try dropping the attached
> >> file into your $VIMRUNTIME folder and see if it makes any
> difference.
> >>
> >> (See ":help rgb.txt" for an explanation of how Vim uses it. IIUC,
on
> >> X11- and Windows-based systems, those colour names' RGB values can
> be
> >> obtained by querying the OS.)
> >
> > Ahh.. found it. 'make install' wasn't copying the 'rgb.txt' to
> > $VIMRUNTIME.
> >
> > It seems that this is a bug because even on the linux machine, 'make
> > install' doesn't copy rgb.txt either. However on the linux machine
> > there are existing copies of rgb.txt in places like /etc/x11/rgb.txt
> > (Ubuntu 7.04) which vim must have picked up which is why it works.
>
> The help mentions /usr/X11R6/lib/X11/ ; I found mine in /usr/share/X11
> (on
> SuSE 10.2)... Apparently there is no single fixed location for that
> file. I
> wonder what the rule is? Any app using colour names should be able to
> find it
> after all.
On Ubuntu 7.04, the following are all symlinked to /etc/X11/rgb.txt
/usr/share/X11/rgb.txt
/usr/lib/X11/rgb.txt
On OSX, there is no rgb.txt on the system at all unless X11 is installed
(which it is not by default). This is why it may be a good thing to
include rgb.txt for the OSX vim builds.
