Syntax Highlighting Problem

Andy> I'm wondering if there is any possible way that a bad Andy> keystroke or bad combination of keystrokes in the script Andy> could cause problems when Xemacs scans the code? Yes, this is possible. Several complex kinds of code interact in font-lock. It is occasionally the case with this kind of problem that simply inserting a newline or a comment in the right place will suddenly allow font-lock to proceed. Such problems are much more common with development versions, though. It's unusual in 21.1. As recommended by Adrian and Craig, you can do binary search on the file. You can use M-x font-lock-fontify-region to fontify regions. Also look at the " *Message-Log*" buffer (the quote marks should be omitted, the leading space is significant) to see if there are any interesting messages or (more interesting!) missing ones. Font-lock is normally pretty verbose, telling you about each of several phases. To see what's "normal", font-lock one buffer that "works." -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."