From: Andreas Leha <email@example.com>
Subject: Re: [RFC] new :post header argument for post-processing of code block results
Date: Tue, 16 Apr 2013 22:42:07 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Eric Schulte <email@example.com> writes:
> Eric S Fraga <firstname.lastname@example.org> writes:
>> Eric Schulte <email@example.com> writes:
>>> I've been wanting to add the ability to post-process the results of a
>>> code block for some time, and some recent threads (e.g.,  and )
>>> could both have benefited from post-processing of code block output.
>>> Does this new header argument seem useful? Any suggestions for better
>>> syntax which don't add too much conceptual or code complexity?
>> Very useful indeed! I don't have a chance to try this out properly now
>> but I know of several previous org files where this would have been very
> Great, I'm happy I wasn't the only one.
No, you were not. Adding lines to tables is one of the cases, I will
use that cool feature from now on.
prev parent reply other threads:[~2013-04-16 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 1:17 [RFC] new :post header argument for post-processing of code block results Eric Schulte
2013-04-01 5:30 ` Aaron Ecay
2013-04-03 14:30 ` Eric Schulte
2013-04-04 2:18 ` Eric Schulte
2013-04-04 9:54 ` Bastien
2013-04-04 12:47 ` Eric Schulte
2013-04-04 12:54 ` Bastien
2014-12-12 16:37 ` Christian Nybø
2013-04-16 12:47 ` Eric S Fraga
2013-04-16 15:23 ` Eric Schulte
2013-04-16 20:42 ` Andreas Leha [this message]
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 \
* 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).