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: disable automatic source block evaluation but allow manual
Date: Thu, 16 Dec 2010 10:48:07 +0100	[thread overview]
Message-ID: <807hfaaw14.fsf@missioncriticalit.com> (raw)
In-Reply-To: 4D09D2EF.8070309@med.uni-goettingen.de

Hi Andreas,

Andreas Leha wrote:
> is there an option (source block header argument) that allows to disable the
> evaluation of the block, but still allows C-c C-c to perform the evaluation?
> The header argument ':eval never' disables the evaluation completely. I'd
> like the C-c C-c to take precedence over this.
>
> So I guess I am looking for something like ':eval manual'

If I rewrite what I understood from your post, you want to make a clear
distinction between:

- allowing evaluation in the Org buffer (when *editing*)
- allowing evaluation when *exporting* it

In fact, I've been thinking at something that annoys me a bit, around this
similar subject: I find it weird to have a buffer that does not contain the
same up-to-date information as the exported (and updated) document.

Arbitrary example:

--8<---------------cut here---------------start------------->8---
* Sh code

#+begin_src sh :results output :exports both
date
#+end_src

#+results:
: Thu, Dec 16, 2010 10:32:36 AM

#+begin_src sh :var thisfile=(buffer-file-name)
echo $(ls -lia "$thisfile" | cut -d " " -f 6) "Bytes in this buffer"
#+end_src

#+results:
: 297 Bytes in this buffer
--8<---------------cut here---------------end--------------->8---

If I add words in that file, the number of characters will go up. That will be
correctly "visible" (shown) in the exported document.

But, *if I don't manually execute* all the code snippets above, they will have
a wrong output...[1]

... moreover, as said previously, it will always (in the above example) be
different from the HTML/PDF version of that buffer. It may lead to erroneous
appreciation of code results, and lead to different and unsynchronized
versions of documents (source Org file, exported documents).

I have a gut feeling that either:

- the export function should not evaluate any code block, or

- when evaluating them for the export, the Org buffer should be updated in the
  same way (results of evaluation copied back into the Org buffer).

I guess the first solution is not a good one. What about the second?

Best regards,
  Seb

Footnotes:
[1] Number of characters won't reflect the new values. And, even if I don't
touch it, the time information will be different between the Org and the
exported files.
-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-12-16  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16  8:50 disable automatic source block evaluation but allow manual Andreas Leha
2010-12-16  9:48 ` Sébastien Vauban [this message]
2010-12-16 13:48   ` Andreas Leha
2010-12-16 14:08   ` Rainer M Krug
2010-12-16 14:16     ` Eric Schulte
2010-12-16 14:43     ` Sébastien Vauban
2010-12-16 14:54       ` Eric Schulte
2010-12-16 13:23 ` Eric Schulte

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=807hfaaw14.fsf@missioncriticalit.com \
    --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).