From: Bastien <bzg@altern.org>
To: nicholas.dokos@hp.com
Cc: Matt Lundin <mdl@imapmail.org>, Org Mode <emacs-orgmode@gnu.org>,
mail@christianmoe.com,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: Slow movement in large buffers
Date: Wed, 16 Mar 2011 02:16:05 +0100 [thread overview]
Message-ID: <87r5a7uap6.fsf@gnu.org> (raw)
In-Reply-To: <6135.1300229813@alphaville.usa.hp.com> (Nick Dokos's message of "Tue, 15 Mar 2011 18:56:53 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Given the evidence that Lawrence Mitchell provided however, it seems clear
> that most of the blame can be placed on overlays - no?
Yes, probably.
I've also experience slow motion in some big files of mine.
One factor was the use of the :ARCHIVE: tag. I tried to remove this
tag, and things were fast again. Another factor might be the use of
folded drawers and #+begin_src environments.
So I guess the problem boils down to 2 factors: the number of *nested
overlays*, and the number of lines in each. How these factors interact
is hard to guess.
Instead of testing from org-issues.org (which is pretty messy), maybe
we can have a testing/overlays.org file with a systematic structure?
#+begin_src org
* headline 1
** A subheading with 100 lines
lines ... lines (x 100)
* headline 2
** A subheading with 100 lines (x 100)
:PROPERTIES:
:LOCATION: Erewhon
:END:
lines ... lines (x 100)
* headline 3
** A subheading with begin_src env and 100 lines (x 100)
#+begin_src emacs-lisp
(defun fixme ()
"Some random defun"
(message "This is not a message")
#+begin_src
lines ... lines (x 100)
* headline 4
** subheading with archive tag and 100 lines :ARCHIVE: (x 100)
lines ... lines (x 100)
#+end_src
Matt, can you build and locally test such a file? Then instrument
next-line when jumping from headline 1 to 2, to 3, to 4?
--
Bastien
next prev parent reply other threads:[~2011-03-16 1:16 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
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 [this message]
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=87r5a7uap6.fsf@gnu.org \
--to=bzg@altern.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--cc=mdl@imapmail.org \
--cc=nicholas.dokos@hp.com \
/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).