In case anyone else is having this problem and is interested in the solution...

According to the xterm maintainer, it was a problem with the way that vim polls xterm for the available number of colors.  In 238, he actually fixed how xterm was reporting it (because vim users were asking him to), but vim doesn't deal with it correctly (yet) and it screws up.  (I hope I didn't mangle his explanation too much)

I fixed this by adding the following to my .vimrc file before I set the color scheme:
set t_Co=256
    - Chris


On Wed, Jan 7, 2009 at 1:30 AM, Cameron Simpson <cs@zip.com.au> wrote:
On 07Jan2009 00:11, Chris Linstid <clinstid@gmail.com> wrote:
| On Tue, Jan 6, 2009 at 6:29 PM, Cameron Simpson <cs@zip.com.au> wrote:
| > You could put specific XTerm.vt100.color0, color1, etc settings in
| > your .Xdefaults file and not be bothered in future if they change the
| > defaults. Check out the section "VT100 Widget Resources" in man xterm.
| >
| > You might also find it useful to examine the file:
| >  /usr/X11/lib/X11/app-defaults/XTerm-color
| > for the MacOSX xterm or:
| >  /opt/local/lib/X11/app-defaults/XTerm-color
| > for the MacPorts version. I presume Fink's version is in the same place
| > but with /sw instead of /opt/local.
| >
| > In fact, changes to that file probably underly the changes you see.
|
| Thanks for the tips Cameron, I'll take a look.
| Do you think it's just a matter of 238 changing the defaults?

I'd have thought so. But I have just installed 238 via MacPorts (since I
still have 237 in MacOSX) and the app-defaults files are unchanged.
--
Cameron Simpson <cs@zip.com.au> DoD#743
_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev