emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <r.m.krug@gmail.com>
To: nicholas.dokos@hp.com
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: I'm tripping over #+BABEL: vs. #+PROPERTY:
Date: Mon, 19 Mar 2012 09:21:47 +0100	[thread overview]
Message-ID: <4F66EC9B.7050202@gmail.com> (raw)
In-Reply-To: <28105.1331828053@alphaville>

Hash: SHA1

On 15/03/12 17:14, Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
>> Hi Nick and Eric,
>> Nick Dokos wrote:
>>> Eric Schulte <eric.schulte@gmx.com> wrote:
>>>> Did you press C-c C-c on each property line after it was written?
>>> Just to clarify: do I really have to C-c C-c on each line? If I add a bunch of them and
>>> then do C-c C-c on one of them, shouldn't that be enough to refresh the setup?
>> I got no reaction on my idea of "automagic C-c C-c" (on 2012-03-04 Sun, see 
>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg52739.html):
>> The "automagic C-c C-c" should be NOT[1] done after each key press or some such. That
>> certainly would be a killer feature, in its real acception: performance would be unbearable.
>> In my mind, automatically (re-)parsing the meta options should be each time the user presses
>> `C-c C-v C-e' (eval code blocks); that is, when the user expects his options to be taken into
>> account.
>> Does it make sense?
>> Best regards, Seb
>> Footnotes:
>> [1] This word was missing (in the original post)!
> Well, it might make sense but you can try it out and let us know:
> - make files with 10, 100, 1000 trivial (or even empty) code blocks, just enough to make sure
> that org-babel-execute-maybe is really called on them: I think that it will be called even on
> empty code blocks, but I'm not sure if there is some optimization in there.
> - measure the time it takes to export each one to html (say).
> - add a call to org-mode-restart into org-babel-execute-maybe, and time the same operation
> again: how significant is the slowdown?
> If the slowdown is bearable in these cases, then it will be bearable in realistic situations,
> where block execution is going to be a much more significant fraction of the total.
> BTW, what's the biggest file you (all, not just Seb) have in terms of the number of code blocks
> it contains? In my case, the largest one had about two dozen code blocks, so the 100 case would
> easily cover me, but I suspect there are much bigger ones out there.

142 - used in literal programming.


> Nick

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys.

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


      parent reply	other threads:[~2012-03-19  8:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 18:23 I'm tripping over #+BABEL: vs. #+PROPERTY: Ken Williams
2012-03-14 18:28 ` Eric Schulte
2012-03-14 18:32   ` Ken Williams
2012-03-14 18:39     ` Eric Schulte
2012-03-14 18:49       ` Ken Williams
2012-03-14 21:21   ` Nick Dokos
2012-03-15 15:15     ` Sebastien Vauban
2012-03-15 16:14       ` Nick Dokos
2012-03-15 16:39         ` Thomas S. Dye
2012-03-18 21:37         ` Sebastien Vauban
2012-03-19  8:21         ` Rainer M Krug [this message]

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:

  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=4F66EC9B.7050202@gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=wxhgmqzgwmuf@spammotel.com \


* 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


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).