Re: cperl mode font-lock problems
matt, are you there? i haven't seen any responses to my messages to you
concerning the syntax-table breakage that a number of people are seeing.
let me clarify about my previous comments. i made a "mea culpa" comment --
with
double-quoted strings, i do indeed need to backslash the $.
but in single-quoted strings, i don't, and i still see the font-lock problem: a
literal like
'^foo.*bar$'
will be font-locked as a runaway string, since the $ will be seen as an escape.
matt, can this be fixed?
Hrvoje Niksic wrote:
Ben Wing <ben(a)666.com> writes:
> well, i should be running with these changes, right?
I think so. Matt originally implemented them to depend on a configure
check *and* a Lisp variable, but I think I persuaded him to get rid of
both.
> i still see the problems, though.
I know. :-( This could be for a number of reasons:
* I could be wrong -- maybe cperl mode doesn't use this feature to get
this effect -- perhaps it uses some other FSF Emacs feature.
* Perhaps Matt's code misbehaves for the things cperl mode uses it for
(Matt, have you ever tested it with cperl mode?)
* Perhaps cperl mode uses the syntax property in a weird way which is
actually incompatible with what we have implemented.
* Finally, perhaps it's something completely silly such as turning on
the feature being triggered with (not (string-match "XEmacs" ...)).
Matt, do you have time to investigate what's going on here?
--
ben
I'm sometimes slow in getting around to reading my mail, so if you
want to reach me faster, call 520-661-6661.
See http://www.666.com/ben/chronic-pain/ for the hell I've been
through.