emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Lawrence Mitchell <wence@gmx.li>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: bug#9610: 24.0.90; org-mode: sluggish response and high CPU utilization with large .org files
Date: Tue, 27 Sep 2011 20:11:06 +0100	[thread overview]
Message-ID: <87lit9vm0l.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87wrcum36m.fsf@gmx.li> (Lawrence Mitchell's message of "Tue, 27 Sep 2011 16:10:25 +0100")

Lawrence Mitchell <wence@gmx.li> writes:

> Steve Revilak wrote:
>
>>>> I'd like to report an org-mode regression issue.  When working with
>>>> large .org files, Emacs 24.0.90 becomes sluggish, and consumes large
>>>> amounts of CPU.
>
>>> If you type this:
>
>>>  M-x set-variable RET bidi-paragraph-direction RET left-to-right RET
>
>>> does the problem go away?
>
>> My bug report contained two scenarios to produce sluggish response and
>> high CPU utilization.  These scenarios were
>
>>  (1) move point to the end of buffer, and start typing
>
>>  (2) Put point in line 1, column zero; press and hold the down (then up)
>>  arrows to move point down (then up) the org-mode buffer.
>
>> Setting bidi-paragraph-direction: left-to-right eliminates the problem
>> with scenario (1).  However, it has no effect on scenario (2).
>
> Setting bidi-display-reordering to nil in the buffer has the
> effect that moving point is no longer jerky for me.

Brilliant!  I have been getting rather annoyed at the jerky movement in
a number of buffers, mostly org, but I knew the problem wasn't due to
org having done timings etc.  Setting this to nil does the job.

What do you recommend is the best way to handle this: in org-mode-hook
for instance?

thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.7 (release_7.7.328.g1a97)

  parent reply	other threads:[~2011-09-27 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110927024957.GP23695@srevilak.net>
2011-09-27  5:31 ` bug#9610: 24.0.90; org-mode: sluggish response and high CPU utilization with large .org files Eli Zaretskii
     [not found] ` <E1R8QGV-0003lq-GR@fencepost.gnu.org>
2011-09-27  6:02   ` Bastien
2011-09-27 13:47   ` Steve Revilak
2011-09-27 17:23     ` Eli Zaretskii
     [not found]   ` <20110927134744.GA959__30964.7548631348$1317134682$gmane$org@KAYAK.com>
2011-09-27 15:10     ` Lawrence Mitchell
2011-09-27 17:23       ` Eli Zaretskii
2011-09-27 19:11       ` Eric S Fraga [this message]
2011-10-01 23:51         ` Tom Davey
     [not found]   ` <87sjnildyw.fsf@altern.org>
2011-09-27 16:47     ` Eli Zaretskii
     [not found]     ` <83sjniexui.fsf@gnu.org>
2011-09-27 17:37       ` Bastien

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=87lit9vm0l.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=wence@gmx.li \
    /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).