Hello again, Another problem I've been having. Again with 21.0.65, but also with various 21 strain betas I've tried over the last few months. I have lots of font-lock-keyword definitions I've historically used in preference to the default ones. I used to be able to reliably configure my font lock colorization by putting in my .emacs, things like: (setq c++-font-lock-keywords c++-font-lock-keywords-gmf) and then whenever I'd load a C++ file, font lock would set font-lock-keywords to the value of c++-font-lock-keywords. Well, that's still how the documentation reads in the font lock code, but in the 21 strain betas, it doesn't seem to work for me. I've been trying to figure this out for a couple of months (okay, I'm not so hot with elisp, just kind of blundering about in the mist), but recently I finally recovered what I was after by doing this: (add-hook 'c++-mode-hook '(lambda () (setq font-lock-keywords c++-font-lock-keywords-gmf))) which is probably proof that I'm an elisp bozo, but anyway, I can't find any other way to get my own keyword alists to overide the ones built into XEmacs. Is this a bug in the XEmacs 21 betas, or can someone explain to me how the situation with personal customization of such things may have changed since the 20 series XEmacsen? This is the one area of XEmacs that seems to give me frustration every time I upgrade, so I always check the FAQ, and it doesn't address this kind of thing. I would be willing to contribute some prose on the subject, if only I knew what to say! Thanks. -- Geoffrey Furnish Actel Corporation furnish(a)actel.com Senior Staff Engineer 955 East Arques Ave voice: 408-522-7528 Placement & Routing Sunnyvale, CA 94086-4533 fax: 408-328-2303