Eric Schulte schulte.eric at gmail.com writes:
Aaron Ecay aaronecay at gmail.com writes:
Yes again
. Do we want to allow :post (message *this*)?
Yes again
Eric,
would you mind posting a sample that shows how to post-process the result
with emacs-lisp?
If I create a buffer
Eric Schulte schulte.e...@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
Eric S Fraga e.fr...@ucl.ac.uk writes:
Eric Schulte schulte.e...@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
Eric Schulte schulte.e...@gmail.com writes:
Eric S Fraga e.fr...@ucl.ac.uk writes:
Eric Schulte schulte.e...@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
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
Bastien, please commit these whenever you want, or let me know and I can
commit them.
Please go ahead.
If you have one minute, you can clone orgweb.git and send a patch
against Changes.org:
~$ git clone org...@orgmode.org:orgweb.git
Bastien b...@altern.org writes:
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
Bastien, please commit these whenever you want, or let me know and I can
commit them.
Please go ahead.
Done.
If you have one minute, you can clone orgweb.git and send a patch
against Changes.org:
Eric Schulte schulte.e...@gmail.com writes:
Done.
Thanks!
--
Bastien
Aaron Ecay aarone...@gmail.com writes:
Hi Eric
2013ko martxoak 31an, Eric Schulte-ek idatzi zuen:
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
If your issue is that (identity *this*) is cumbersome, then I would
agree. What about if we change `org-babel-read' as with the attached
patch s.t. *any* variable with ear-muffs will be read as Emacs Lisp,
allowing this simpler alternative.
The attached patches change to the more natural
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.
The attached patch [3] adds a new :post header argument, which may be
used to
Hi Eric
2013ko martxoak 31an, Eric Schulte-ek idatzi zuen:
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.
This looks very
11 matches
Mail list logo
