emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ob-R] combine :post and :colnames
Date: Mon, 26 Jan 2015 18:31:22 +0100	[thread overview]
Message-ID: <871tmhcutx.fsf@gmx.us> (raw)
In-Reply-To: <874mrege0y.fsf@gmail.com> (Aaron Ecay's message of "Mon, 26 Jan 2015 03:08:29 -0500")

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]


Aaron Ecay <aaronecay@gmail.com> writes:

> 2015ko urtarrilak 25an, Rasmus-ek idatzi zuen:
>> Should add a note on this to the manual?  Or is it clear enough as it
>> is?
> I think it would be a good idea to add a note about this in the manual.
> Perhaps in the form of another example in the node for the :post header
> argument (info "(org) post") which shows how to use :post to process a
> tabular result.

I'm a bit busy right now, but here's a quick proposal.  If you are happy
with it, I'll push it.


With monopolies the cake is a lie!

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org.texi-New-example-on-babel-post-header.patch --]
[-- Type: text/x-diff, Size: 2006 bytes --]

From 721926ad040c3bf0d46660bdbf2543ea9645b3aa Mon Sep 17 00:00:00 2001
From: rasmus <rasmus@gmx.us>
Date: Mon, 26 Jan 2015 18:24:39 +0100
Subject: [PATCH] org.texi: New example on babel :post header

* org.texi (post): Clarification and new example.
 doc/org.texi | 32 +++++++++++++++++++++++++++++---
 1 file changed, 29 insertions(+), 3 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 65c9309..defd015 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15979,10 +15979,11 @@ code block execution.  When a post argument is given, the results of the code
 block will temporarily be bound to the @code{*this*} variable.  This variable
 may then be included in header argument forms such as those used in @ref{var}
 header argument specifications allowing passing of results to other code
-blocks, or direct execution via Emacs Lisp.
+blocks, or direct execution via Emacs Lisp.  Additional header arguments may
+be passed to the @code{:post}-function.
-The following example illustrates the usage of the @code{:post} header
+The following two examples illustrate the usage of the @code{:post} header
+argument.  The first example shows how to attach a attribute-line via @code{:post}.
 #+name: attr_wrap
@@ -16007,6 +16008,31 @@ argument.
 @end example
+The second examples shows how to use @code{:post} together with the
+@code{:colnames} header argument.
+#+name: round-tbl
+#+begin_src emacs-lisp :var tbl="" fmt="%.3f"
+  (mapcar (lambda (row)
+            (mapcar (lambda (cell)
+                      (if (numberp cell)
+                          (format fmt cell)
+                        cell))
+                    row))
+          tbl)
+#+begin_src R :colnames yes :post round-tbl[:colnames yes](*this*)
+|   foo |
+| 1.371 |
+@end example
 @node prologue
 @subsubsection @code{:prologue}
 @cindex @code{:prologue}, src header argument

      reply	other threads:[~2015-01-26 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 20:38 [ob-R] combine :post and :colnames Rasmus
2015-01-25 21:26 ` Aaron Ecay
2015-01-25 21:56   ` Rasmus
2015-01-26  8:08     ` Aaron Ecay
2015-01-26 17:31       ` Rasmus [this message]

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:

  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=871tmhcutx.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \


* 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


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).