|
From: | Lennart Borgman |
Subject: | Re: Elisp syntax hilighting problem |
Date: | Sun, 23 Apr 2006 01:22:25 +0200 |
User-agent: | Thunderbird 1.5.0.2 (Windows/20060308) |
Andreas Schwab wrote:
I happens sometimes but not always. One way I have seen to reproduce it is to delete the line after defconst and before next declaration. I just tested it - it worked for me a couple of times (ie I could see the problem) and then everything looked ok again.Lennart Borgman <address@hidden> writes:The defconst below sometimes upset the syntax highlighting so that the function following it is in the same face as the string:I cannot reproduce that here. Can you give more details about the situation where it occurs?
(defconst rng-in-attribute-value-regex (replace-regexp-in-string "w" xmltok-ncname-regexp "<w\\(?::w\\)?\ \\(?:[ \t\r\n]+w\\(?::w\\)?[ \t\r\n]*=\ [ \t\r\n]*\\(?:\"[^\"]*\"\\|'[^']*'\\)\\)*\ [ \t\r\n]+\\(w\\(:w\\)?\\)[ \t\r\n]*=[ \t\r\n]*\ \\(\"[^\"]*\\|'[^']*\\)\\=" t t)) More problems: The \\= is not marked.There are no builtin rules for marking this. Only grouping constructs have special faces.
Oh, I see. Maybe it should be marked?
The two [ at beginning of line is marked with a red face.This is a feature. It marks characters (by default those of open paren syntax at the start of a line) that breaks the simple-minded parsing of beginning-of-defun. Prepend a backslash to avoid that.
Thanks.
[Prev in Thread] | Current Thread | [Next in Thread] |