Re: cperl-mode quick question/gripe
-- "Karl M. Hegbloom" <karlheg(a)microsharp.com> spake thusly:
Anyone know if cperl has ever been patched by anybody so that:
o Apostophe inside POD and "here" documents doesn't cause
font-locking to believe that a single quoted string is running away
on through your code until the next single quote
o Dollar sign at the end of a regexp, single quoted string, or paren
quoted (q) string is not seen as the special $' variable
o Quotation marks inside regexps are not seen as normal.
Actually the patch to get this stuff working was applied (by me) to
XEmacs itself. All these features should "just work" now, but may
require some configuration of cperl-mode. Everything works for me, but
I'm not certain how to tell you to get from where you are to where I
am, although I know that running at least 21.4 is required.
I would, however, be very happy to work with you to get this working.
I've looked at my customization settings, and I notice the following:
(custom-set-variables
...
'(cperl-syntaxify-by-font-lock t)
'(cperl-use-syntax-table-text-property t)
'(cperl-use-syntax-table-text-property-for-tags t)
'(cperl-font-lock t)
...)
I suspect that all of these are necessary for proper operation. Try
setting them to true (ideally through the Customize interface unless
your preference is otherwise) and let me know if that works.
I notice that three of them are dependant on the variable
'parse-sexp-lookup-properties being bound. Unfortunately when I ported
syntax-table properties (extents) from Emacs I changed some variable
names, this one included. Presumably cperl-mode needs to be patched to
check for the correct variable on XEmacs.
Attachments:
- attachment.sig (application/pgp-signature — 232 bytes)