Re: Elisp syntax hilighting problem

[Andreas Schwab]

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.

> 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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."