Re: cperl-mode quick question/gripe
On Thu, Jul 26, 2001 at 12:15:14PM -0700, Matt Tucker wrote:
-- Damien Neil <neild(a)misago.org> spake thusly:
> Do you have a complete list of the symbol names that were changed?
No, but I could compile one.
That would be useful; I'd like to make certain that cperl isn't
using any other renamed variables.
However, I can certainly see the value in compatibility. Presumably
the
best thing to do would be to either rename the variable(s) in question
or provide aliases to them to maintain GNU Emacs compatibility. Of the
two, I think I prefer the aliasing unless someone has a strong argument
against it.
Aliasing would be fine with me, but I don't think I'd ever use anything
other than the GNU Emacs-compatible ones. As long as it is possible to
write code that works on both Emacsen without sprinkling conditionals
all over the place, however, I'll be happy.
> After patching cperl-mode.el, things do seem to work much
better.
> Constructs like "$foo = q{troz ' }" are handled properly. There
> seem to be some problems with font-lock. When I first load a file,
> the amount of decoration is higher than what is applied when editing
> the file. For example, the word "new" in the phrase "sub new
{}"
> is rendered using font-lock-function-name-face when I first load
> a Perl file, but is rendered with the default face when I type it
> into an existing buffer.
I don't have this issue, so there must be further differences between
my system and yours. What version of cperl-mode are you using?
4.32, but taken from the xemacs-packages tree. I'm not certain if
there are changes from the baseline 4.32; I may hunt down the latest
non-XEmacs-specific cperl and try that.
- Damien