emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-src-fontify-natively makes things very, very slow
Date: Thu, 17 Mar 2011 21:34:45 +0100	[thread overview]
Message-ID: <804o71triy.fsf@somewhere.org> (raw)
In-Reply-To: 87ipvhiou8.fsf@ucl.ac.uk

Hi all,

Eric S Fraga wrote:
> Julian Burgos <jmburgos-lfcS8c3Mqgg@public.gmane.org> writes:
>> I was very excited to discover org-src-fontify-natively, but I´m not having
>> a good experience with it. When it is on, org-mode becomes very slow while
>> typing into a code block. This happens regardless of the size of the file
>> or number of blocks, and the slow down is very noticeable. Each keystroke
>> takes about half a second to appear in screen. Typing outside of the code
>> blocks everything works fine. Turning off font-lock-verbose and
>> global-linum-mode did not make any difference. I´m running OrgMode 7.5 and
>> GNU Emacs 23.2.1. on Windows XP.
>>
>> Any ideas?

Idem for me. Slow(er) in Org buffer itself.

> If you edit the source code block in its native mode (C-c',
> =org-edit-special=), is it fast or slow?

Fast(er) in dedicated buffer.

> In any case, this may be related to the thread on slow behaviour
> discussed on this list the past few days.  Does the response improve if
> you kill the buffer and load the file again?

Maybe this is (partly?) due to the overlay I added:

#+begin_src emacs-lisp
                (overlay-put (make-overlay beg1 block-end)
                             'face 'org-block-background))
#+end_src

in function

#+begin_src emacs-lisp
(defun org-fontify-meta-lines-and-blocks (limit)
#+end_src

in file org.el.

Best regards,
  Seb

-- 
Sébastien Vauban

  reply	other threads:[~2011-03-17 20:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 13:59 org-src-fontify-natively makes things very, very slow Julian Burgos
2011-03-17 18:28 ` Eric S Fraga
2011-03-17 20:34   ` Sébastien Vauban [this message]
2011-03-18  0:11     ` Julian Burgos
2011-03-18  8:38     ` Eric S Fraga
2011-03-18 12:44       ` Julian Burgos
2011-03-19  9:20       ` Sébastien Vauban
2011-03-19 12:28         ` suvayu ali
2011-03-19 20:37           ` Eric S Fraga
2011-03-19 20:34         ` Eric S Fraga
2011-03-20  4:23           ` Le Wang
2011-03-20 19:41             ` Eric S Fraga
2011-03-21  2:37               ` Le Wang
2011-03-21 13:57                 ` Eric Schulte
2011-03-21 17:06                   ` Eric S Fraga
2011-03-21 22:23                     ` Sébastien Vauban
2011-03-22  9:18                       ` Ulf Stegemann
2011-03-29 14:49                       ` Matt Lundin
2011-03-29 16:49                         ` Eric S Fraga
2011-03-30  7:34                         ` Sébastien Vauban
2011-04-28 20:59                     ` Carsten Dominik
2011-04-28 23:32                       ` Eric S Fraga
2011-04-30 19:45                         ` Eric S Fraga
2011-05-01 13:37                           ` Carsten Dominik
2011-03-29 14:12           ` Matt Lundin
2011-03-29 16:44             ` 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=804o71triy.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).