From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Matt Lundin <mdl@imapmail.org>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Slow movement in large buffers
Date: Tue, 15 Mar 2011 18:42:01 +0100 [thread overview]
Message-ID: <8D34911D-B334-4543-9D6F-4A3A34F27BCF@gmail.com> (raw)
In-Reply-To: <87fwqowk4v.fsf@ucl.ac.uk>
On 15.3.2011, at 15:09, Eric S Fraga wrote:
> Hello,
>
> following up on this issue, I have just run into it again. I'm editing
> a not very large document and suddenly things slowed down, mostly but
> not exclusively for "next-line":
>
> --8<---------------cut here---------------start------------->8---
> next-line 18 2.1547069999 0.1197059444
> previous-line 19 0.4066669999 0.0214035263
> org-mode-flyspell-verify 16 5.299...e-05 3.312...e-06
> --8<---------------cut here---------------end--------------->8---
>
> This happened when I started a new source code block (gnuplot, to be
> exact) but didn't type in the end_src line for a while. The problem
> seems to be due to font-locking and it tries to font-lock the whole
> document initially. When I eventually get around to typing the end_src
> line, it font-locks correctly but things are slow thereafter. There
> seems to be some hysteresis loop in the code...
This sounds like a bug that needs to be fixed in the block fontifications,
maybe a limit for how far to search for the end line. regular expressions
that match many lines need to be carefully constructed - there are possible
backtracking traps that can make the matching time scale as the number of
characters squared.
- Carsten
>
> If I kill the buffer and reload the file, everything is fine.
>
> --8<---------------cut here---------------start------------->8---
> next-line 17 0.0655900000 0.0038582352
> previous-line 17 0.0115249999 0.0006779411
> org-mode 1 0.007178 0.007178
> org-fontify-meta-lines-and-blocks 25 0.0022920000 9.168...e-05
> org-set-startup-visibility 1 0.001619 0.001619
> org-raise-scripts 25 0.0013889999 5.555...e-05
> --8<---------------cut here---------------end--------------->8---
>
> Dramatic difference!
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.5 (release_7.5.38.gf8c6.dirty)
>
next prev parent reply other threads:[~2011-03-15 17:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 3:25 Slow movement in large buffers Matt Lundin
2011-03-15 5:03 ` Carsten Dominik
2011-03-15 12:51 ` Matt Lundin
2011-03-15 10:58 ` Eric S Fraga
2011-03-15 12:54 ` Matt Lundin
2011-03-15 14:09 ` Eric S Fraga
2011-03-15 17:42 ` Carsten Dominik [this message]
2011-03-15 11:18 ` Carsten Dominik
2011-03-15 12:33 ` Lawrence Mitchell
2011-03-15 12:50 ` Matt Lundin
2011-03-15 14:15 ` Nick Dokos
2011-03-15 15:51 ` Matt Lundin
2011-03-15 17:39 ` Carsten Dominik
2011-03-15 22:00 ` Christian Moe
2011-03-15 22:56 ` Nick Dokos
2011-03-15 23:13 ` Christian Moe
2011-03-16 3:48 ` Nick Dokos
2011-03-16 1:16 ` Bastien
2011-03-18 0:37 ` Matt Lundin
2011-03-15 16:11 ` Chris Randle
2011-03-15 16:41 ` MidLifeXis at PerlMonks
2011-03-15 17:14 ` Scott Randby
2011-03-15 17:18 ` Erik Iverson
2011-03-15 17:38 ` Carsten Dominik
2011-05-11 0:41 ` Carmine Casciato
2011-05-12 6:59 ` Eric S Fraga
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8D34911D-B334-4543-9D6F-4A3A34F27BCF@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).