emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
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: <877gk28axs.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87mwsycxaa.fsf@gmail.com

Eric Schulte <schulte.eric@gmail.com> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> Eric Schulte <schulte.eric@gmail.com> writes:
>>
>>> Hi,
>>>
>>> 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., [1] and [2])
>>> 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
>> useful.
>>
>
> 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.

Regards,
Andreas

      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]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=877gk28axs.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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