From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aaron Ecay <aaronecay@gmail.com>
Subject: Re: update on missing :parameters in code blocks
Date: Sun, 21 Sep 2014 22:39:32 -0400
Message-ID: <8738bkqsyj.fsf@gmail.com>
References: <m261ggvc5t.fsf@andrew.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38452)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1XVtXb-0002FA-Lp
	for emacs-orgmode@gnu.org; Sun, 21 Sep 2014 22:40:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1XVtXS-00027s-LW
	for emacs-orgmode@gnu.org; Sun, 21 Sep 2014 22:39:51 -0400
Received: from mail-qc0-x234.google.com ([2607:f8b0:400d:c01::234]:61949)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1XVtXS-00025W-Gc
	for emacs-orgmode@gnu.org; Sun, 21 Sep 2014 22:39:42 -0400
Received: by mail-qc0-f180.google.com with SMTP id m20so5366947qcx.25
	for <emacs-orgmode@gnu.org>; Sun, 21 Sep 2014 19:39:36 -0700 (PDT)
In-Reply-To: <m261ggvc5t.fsf@andrew.cmu.edu>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: John Kitchin <jkitchin@andrew.cmu.edu>, emacs-orgmode@gnu.org

Hi John,

Look at the functions =E2=80=98org-babel-exp-src-block=E2=80=99 which calls
=E2=80=98org-babel-exp-do-export=E2=80=99, which calls =E2=80=98org-babel-e=
xp-code=E2=80=99.  The tl;dr
version is that indeed the babel export machinery does change the code
block in substantial ways, including the removal of parts of it.

This plays merry hell with the cache mechanism, as you might imagine
(different header args at different points -> the sha1 hash changes).  A
year or more ago I worked on a patch to overhaul this system.  I got
partway through before giving up, because it turned into a massive
undertaking and because it became clear that the cache mechanism would
not be very reliable/useful for my needs anyway.  But IMHO it remains an
imperfection in the interface between babel and the new parser, and it
might be possible to avoid the necessity of doing this sort of
destructive modification during export.  Along the way simplification of
the code might also be possible.

Let me know if you=E2=80=99re interested; I may be able to dig the old
half-patch out of a disused git branch somewhere.  It may have bitrotted
some, but it may also be useful.

--=20
Aaron Ecay