From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erich Neuwirth Subject: Inline and executing the document Date: Wed, 19 Sep 2012 15:44:40 +0200 Message-ID: Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:37321) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEKaH-0006QN-SJ for emacs-orgmode@gnu.org; Wed, 19 Sep 2012 09:44:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEKaB-0001t2-Ld for emacs-orgmode@gnu.org; Wed, 19 Sep 2012 09:44:57 -0400 Received: from grace.univie.ac.at ([131.130.3.115]:33410) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEKaB-0001rS-BK for emacs-orgmode@gnu.org; Wed, 19 Sep 2012 09:44:51 -0400 Received: from justin.univie.ac.at ([131.130.3.111] helo=justin.univie.ac.at) by grace.univie.ac.at with esmtp (Exim 4.80) (envelope-from ) id 1TEKa7-0008Ap-EN for emacs-orgmode@gnu.org; Wed, 19 Sep 2012 15:44:47 +0200 Received: from 188045001103.atmpu0057.highway.a1.net ([188.45.1.103] helo=[172.20.10.2]) by justin.univie.ac.at with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1TEKa6-0003Ll-8L for emacs-orgmode@gnu.org; Wed, 19 Sep 2012 15:44:47 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org emacs-orgmode@gnu.org" The following examples shows some issues=20 #+title: Inline formatting Inline code examples src_emacs-lisp{(+ 2 3)} src_emacs-lisp[:results raw]{(2 + 5)}=20 #+BEGIN_SRC emacs-lisp (+ 11 12) #+END_SRC #+RESULTS: : 23 #+BEGIN_SRC emacs-lisp :results raw (+ 11 13) #+End_Src ################################## In 3 of the 4 examples running the code repeatedly=20 with C-c C-c will produce multiple copies of the output. Only the default code block (example 3) "knows" to delete the old result when a new one is produced. If one is not careful about this, one can easily produce inconsistent = documents. Changing the code but not the old results will keep different results = within the document and these results will also be exported. A solution would be to have markers like #+begin_results #+end_results Then, org mode could know what exactly to delete. This would need to me modified for inline src statements bit should be = doable. I think this could help with the general concept of producing consistent = reproducible research documents. Anny suggestions regarding this issue? Erich