emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: I'm tripping over #+BABEL: vs. #+PROPERTY:
Date: Thu, 15 Mar 2012 12:14:13 -0400	[thread overview]
Message-ID: <28105.1331828053@alphaville> (raw)
In-Reply-To: Message from "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> of "Thu, 15 Mar 2012 16:15:05 BST." <80y5r1sxom.fsf@somewhere.org>

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.


  reply	other threads:[~2012-03-15 16:14 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 [this message]
2012-03-15 16:39         ` Thomas S. Dye
2012-03-18 21:37         ` Sebastien Vauban
2012-03-19  8:21         ` Rainer M Krug

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=28105.1331828053@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --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).