From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: Slow movement in large buffers Date: Wed, 16 Mar 2011 02:16:05 +0100 Message-ID: <87r5a7uap6.fsf@gnu.org> References: <87d3ltjc8x.fsf@fastmail.fm> <17242340-A14F-495A-B144-20C96D52B620@gmail.com> <7205.1300198547@alphaville.dokosmarshall.org> <871v28tm9u.fsf@fastmail.fm> <4D7FE16F.10305@christianmoe.com> <6135.1300229813@alphaville.usa.hp.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=40887 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PzfLi-0003IC-0d for emacs-orgmode@gnu.org; Tue, 15 Mar 2011 21:16:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PzfLg-0006mL-TP for emacs-orgmode@gnu.org; Tue, 15 Mar 2011 21:16:29 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:43803) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PzfLg-0006mG-MW for emacs-orgmode@gnu.org; Tue, 15 Mar 2011 21:16:28 -0400 Received: by wwc33 with SMTP id 33so1304941wwc.30 for ; Tue, 15 Mar 2011 18:16:27 -0700 (PDT) In-Reply-To: <6135.1300229813@alphaville.usa.hp.com> (Nick Dokos's message of "Tue, 15 Mar 2011 18:56:53 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: nicholas.dokos@hp.com Cc: Matt Lundin , Org Mode , mail@christianmoe.com, Carsten Dominik Nick Dokos 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