Re: 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? Stephen> Yes, this is possible. Several complex kinds of code Stephen> interact in font-lock. It is occasionally the case with Stephen> this kind of problem that simply inserting a newline or a Stephen> comment in the right place will suddenly allow font-lock Stephen> to proceed. Stephen> Such problems are much more common with development Stephen> versions, though. It's unusual in 21.1. Stephen> As recommended by Adrian and Craig, you can do binary Stephen> search on the file. You can use M-x Stephen> font-lock-fontify-region to fontify regions. Stephen> Also look at the " *Message-Log*" buffer (the quote marks Stephen> should be omitted, the leading space is significant) to Andy, just use M-x show-message-log to access it. Stephen> see if there are any interesting messages or (more Stephen> interesting!) missing ones. Font-lock is normally pretty Stephen> verbose, telling you about each of several phases. Stephen> To see what's "normal", font-lock one buffer that Stephen> "works." Stephen> -- Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Stephen> Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 Stephen> _________________ _________________ _________________ _________________ Stephen> What are those straight lines for? "XEmacs rules." -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/