From: Julian Burgos <jmburgos@uw.edu>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Re: org-src-fontify-natively makes things very, very slow
Date: Fri, 18 Mar 2011 12:44:49 +0000 [thread overview]
Message-ID: <AANLkTi=uL3=nR4V55iiMnBF1C91xYXPyX=-aTOkomFJH@mail.gmail.com> (raw)
In-Reply-To: <87bp18su1a.fsf@ucl.ac.uk>
Hi Eric,
I have a small function to insert the opening and ending of an R code
block bound to a key, so I always edit the code between a
"#+begin_src R" and "#+end_src R". I still get a considerable
slowdown, even with an empty document with a single line of code.
Julian
On Fri, Mar 18, 2011 at 8:38 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>
> [...]
>
>> 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
>
> This could indeed be one cause, especially depending on what this does
> when there is no block-end line, or at least not anywhere near in the
> buffer. I seem to get a slowdown when I have a situation like this:
>
> #+begin_example
>
> [... some text ...]
> #+begin_src somelanguage
> [... text which is part of the source block...]
> <point here>
>
> [... lots of other text ...]
> [... including other source blocks]
>
> #+end_example
>
> where there is no matching #+end_src or, more precisely, the
> next #+end_src line is one that does not belong to this current source
> block. Your search (in org.el) for the end of the block assumes that it
> does have the end statement in place already. I'm not sure how to fix
> this because it's an ill-defined situation.
>
> It may be worthwhile making the overlay optional? Although I must admit
> that I like it!
>
> My solution, by the way, is to insert the #+end_src line immediately
> upon writing a #+begin_src line and then back up a line to start writing
> the code.
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.5 (release_7.5.77.g74268)
>
>
--
Julian Mariano Burgos
Hafrannsóknastofnunin/Marine Research Institute
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax: +354-5752001
Netfang/Email: julian@hafro.is, jmburgos@uw.edu
next prev parent reply other threads:[~2011-03-18 12:45 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
2011-03-18 0:11 ` Julian Burgos
2011-03-18 8:38 ` Eric S Fraga
2011-03-18 12:44 ` Julian Burgos [this message]
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='AANLkTi=uL3=nR4V55iiMnBF1C91xYXPyX=-aTOkomFJH@mail.gmail.com' \
--to=jmburgos@uw.edu \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).