From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Schulte <eric.schulte@gmx.com>
Subject: Re: Is it possible to include #+call lines in HTML export?
Date: Mon, 23 Jan 2012 12:54:28 -0700
Message-ID: <87pqeaqjnv.fsf@gmx.com>
References: <CADzxs1=bBRnHkBTAtHNP1j2AfF2OBNhY6pX-zGP-srWXK18gYQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:35178)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.schulte@gmx.com>) id 1RpPyO-0006hr-34
	for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 14:54:37 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eric.schulte@gmx.com>) id 1RpPyM-0007FT-Ok
	for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 14:54:36 -0500
Received: from mailout-us.gmx.com ([74.208.5.67]:45700)
	by eggs.gnu.org with smtp (Exim 4.71)
	(envelope-from <eric.schulte@gmx.com>) id 1RpPyM-0007FG-7s
	for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 14:54:34 -0500
In-Reply-To: <CADzxs1=bBRnHkBTAtHNP1j2AfF2OBNhY6pX-zGP-srWXK18gYQ@mail.gmail.com>
	(Leo Alekseyev's message of "Fri, 20 Jan 2012 17:12:12 -0600")
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: Leo Alekseyev <dnquark@gmail.com>
Cc: Emacs orgmode <emacs-orgmode@gnu.org>

Leo Alekseyev <dnquark@gmail.com> writes:

> Currently, my org files look something like this:
>
> * And now, let's do the analysis !
> #+call: foo(bar)
>
> #+results:
> :  earth-shattering results
> :  gonna land me a Nobel /and/ a Fields!
>
> But because #+call is not exported, it's not clear what function was
> called and with what parameters.  It makes a lot of sense for it to be
> included in the export (unless its evaluation is turned off via e.g.
> :eval no-export), but I can't find an option for this.
>

Currently what you describe is not possible.  Call lines are by default
replaced with their results on export.

...

Alright, I just pushed up an addition which allows the specification of
a call line export template to include information like the name of the
call line used to generate the results.  For example, add the following
to your config and export a buffer with call lines.

(setq org-babel-exp-call-line-template "\n: call: %line")

Best,

>
> --Leo
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/