From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: C mode too slow
Date: Sun, 12 Jun 2011 20:38:11 +0000 [thread overview]
Message-ID: <20110612203811.GA10061@acm.acm> (raw)
Hi, Stefan
>> _and_ because editing lisp.h is virtually impossible these days. I
>> have to use an old Emacs - almost each editing step takes about 15
>> secs here with the more recent Emacs versions :-(
> I tend to find editing code such as lisp.h too slow as well. Can we
> do something about it?
lisp.h is slow in "brace desserts", since CC Mode uses braces as anchor
points, particularly whilst font locking. This should have been fixed
by the optimisation of c-parse-state.
However, comparing the trunk with Emacs 23.3 the number of calls to
c-parse-state has increased by a factor of ~9, cancelling out the
optimisation. :-( I'm looking to see why this has happened.
I'm actually looking at a large file (without a single brace) called
AT91SAM9263_INC.h, the one which triggered this optimisation. What
seems to me slow in lisp.h is scrolling over areas which haven't yet
been fontified since loading. Once that is done, I think things move at
a decent speed. Is there anything particular, other than initial
scrolling, which is very slow in lisp.h?
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2011-06-12 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 20:38 Alan Mackenzie [this message]
2011-06-13 14:59 ` C mode too slow Alan Mackenzie
2011-06-20 21:10 ` Stefan Monnier
[not found] <4DEDC752.7090604@gmx.at>
2011-06-07 12:23 ` Stefan Monnier
2011-06-07 14:12 ` Eli Zaretskii
2011-06-07 17:57 ` Stefan Monnier
2011-06-07 18:45 ` Nikodemus Siivola
2011-06-08 1:42 ` Stefan Monnier
2011-06-07 20:14 ` Eli Zaretskii
2011-06-08 1:43 ` Stefan Monnier
2011-06-08 7:30 ` Jindrich Makovicka
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=20110612203811.GA10061@acm.acm \
--to=acm@muc.de \
--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.