From: Matt Lundin <mdl@imapmail.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Slow movement in large buffers
Date: Tue, 15 Mar 2011 08:54:11 -0400 [thread overview]
Message-ID: <87fwqoy26k.fsf@fastmail.fm> (raw)
In-Reply-To: <87wrk0r6p3.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 15 Mar 2011 10:58:32 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Matt Lundin <mdl@imapmail.org> writes:
> Interesting. It doesn't take 3 seconds on my system (Intel(R)
> Pentium(R) D CPU 2.80GHz) but there is a noticeable delay using C-n to
> move from =* Other= to =* Closed issues=. However, using C-cC-n to move
> has no delay at all and moving backwards (either C-p or C-cC-p) also
> exhibits no delay.
You are right. The slowness only occurs when using next-line and
previous-line. When I use the functions for navigating outlines (e.g.,
outline-next-visible-heading), the movement is instantaneous.
Best,
Matt
next prev parent reply other threads:[~2011-03-15 12:54 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 [this message]
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
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=87fwqoy26k.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.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).