From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Teege <matthias-omd@mteege.de>
Subject: Re: Passing a table to org-babel shell script
Date: Sun, 7 Feb 2010 10:01:15 +0100
Message-ID: <20100207090115.GA11136@cab>
References: <20100124094734.GA10344@cab> <87wryqfc3b.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ne33E-00074U-ST
	for emacs-orgmode@gnu.org; Sun, 07 Feb 2010 04:03:32 -0500
Received: from [199.232.76.173] (port=46625 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ne33E-000747-Cx
	for emacs-orgmode@gnu.org; Sun, 07 Feb 2010 04:03:32 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <matthias-omd@mteege.de>) id 1Ne339-00081n-St
	for emacs-orgmode@gnu.org; Sun, 07 Feb 2010 04:03:32 -0500
Received: from port-87-193-189-27.static.qsc.de ([87.193.189.27]:49099
	helo=crn.mteege.de) by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <matthias-omd@mteege.de>) id 1Ne339-0007zh-7G
	for emacs-orgmode@gnu.org; Sun, 07 Feb 2010 04:03:27 -0500
Content-Disposition: inline
In-Reply-To: <87wryqfc3b.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

On 11:33 Sat 06 Feb, Eric Schulte wrote:

Moin,

thanks for your reply

> 1) allowing the user to specify a separator with a header argument as
>    follows
>    #+begin_src sh :var table=sec :separator ,
>      cat <<EOF
>      $table
>      EOF
>    #+end_src
>    
>    which would result in something like
> 
>    : "Hello, World"

I like this idea because it is what I would expect. In my first
"experiment", I assumed that I can use the "|" as a separator. I would
like to use a table as input form and pipe the rows to a shell script
written in org-babel. Sometimes it is easier to proccess data with
awk instead of using elisp. So my example is a bit misleading.

> 2) writing the table to a tab or comma separated file and then
>    replacing =$table= in the source block body with the path to the
>    file name, s.t. something like

IMHO it is not necessary under Unix. Reading from stdin is usual. But it
maybe different under Windows.

Many thanks
Matthias