From: bkuhn@ebb.org (Bradley M. Kuhn)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: sluggish behavior in cperl-mode on a large file (included)
Date: Fri, 23 Feb 2007 11:27:01 -0500 [thread overview]
Message-ID: <87abz47sbu.fsf@shipitfish.net> (raw)
In-Reply-To: <jwvhctdmpiw.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 23 Feb 2007 00:08:57 -0500")
>> I am running emacs-snapshot from debian, dated 2006-12-18.
>> I have noticed that editing it is extremely slow in cperl-mode with
>> font-lock on.
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Not directly answering your question or addressing your problem: have
> you tried to use plain perl-mode instead? In Emacs-22, it does much
> better syntax-highlighting that in Emacs-21, pretty close to what
> cperl-mode does.
I noticed that perl-mode has gotten a lot better, but I am unfortunately
used to a lot of things that I get from cperl-mode. (For example, I
prefer its default indenting behavior to that of perl's mode, and I like
some fo the construct auto completion stuff). For the moment, the work
around you suggest is what I'm using for those files I have with lots of
large heredoc-strings.
Someone on #emacs suggested that maybe a "new regex engine" in Emacs 22
was to blame. This seemed like a bit dubious to me, but I thought I'd
mention it. The profiler clearly is spending a lot of time finding and
doing the fontify-ing of various constructs, and the most time seems to be
spent on things that are particular long (like heredoc strings).
-- bkuhn
next prev parent reply other threads:[~2007-02-23 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 7:19 [bkuhn@ebb.org: sluggish behavior in cperl-mode on a large file (included)] Richard Stallman
2007-02-23 5:08 ` sluggish behavior in cperl-mode on a large file (included) Stefan Monnier
2007-02-23 16:27 ` Bradley M. Kuhn [this message]
2007-02-26 3:35 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2007-02-20 17:56 Bradley M. Kuhn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87abz47sbu.fsf@shipitfish.net \
--to=bkuhn@ebb.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.