Bastien writes:
> 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?
I'm on the job. :)
I'll write back with an official report. Suffice it to say that my early
experiments show org-mode cruising through the examples you
Christian Moe wrote:
> On 3/15/11 11:56 PM, Nick Dokos wrote:
> Given the five previous-lines in your profile, I suspect that
> > one or two were much longer than the others which skewed the average.
>
> Actually not, I was going back and forth over the same two lines, and
> previous-line was
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 th
On 3/15/11 11:56 PM, Nick Dokos wrote:
Given the five previous-lines in your profile, I suspect that
one or two were much longer than the others which skewed the average.
Actually not, I was going back and forth over the same two lines, and
previous-line was fairly stable at around 1.2 second
Christian Moe wrote:
>
> > Yes, hardware is indeed a factor here. I'm using a dual-core Atom processor
> > with 2GB of memory.
> >
> > Matt
> >
>
> I'm not so sure about the hardware factor.
>
> I'm on a seven-year-old G4 Mac PPC laptop with 768 MB RAM.
>
> Over the same folded headings in a
Yes, hardware is indeed a factor here. I'm using a dual-core Atom processor
with 2GB of memory.
Matt
I'm not so sure about the hardware factor.
I'm on a seven-year-old G4 Mac PPC laptop with 768 MB RAM.
Over the same folded headings in a freshly pulled org-issues (Other to
Development Tas
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
On 15.3.2011, at 16:51, Matt Lundin wrote:
> Nick Dokos writes:
>
>> FWIW, I opened org-issues.org and followed Matt's lead: at first, I got
>> almost instant response going from Other to Closed (using arrow-down)
>> and a slight hesitation (< 0.5s) going from Other to the previous
>> headline
Nick Dokos writes:
> FWIW, I opened org-issues.org and followed Matt's lead: at first, I got
> almost instant response going from Other to Closed (using arrow-down)
> and a slight hesitation (< 0.5s) going from Other to the previous
> headline (Development Tasks). After noodling around for a whi
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
Eric S Fraga writes:
> Matt Lundin 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 backwa
Carsten Dominik writes:
> DO you have flyspell turned on?
>
Yes, but the same results occur with flyspell turned off. (See my
response to your other email.)
Best,
Matt
Carsten Dominik writes:
> On Mar 15, 2011, at 4:25 AM, Matt Lundin wrote:
>
>> I've been navigating the org-issues file (14000+ lines) and have found
>> movement within the file to be fairly slow. Sometimes Emacs will lock up
>> for several seconds.
>>
>> For instance, to move from the level one
13 matches
Mail list logo
