Re: [O] [RFC] new :post header argument for post-processing of code block results

2014-12-12 Thread Christian Nybø
Eric Schulte gmail.com> writes: > > Aaron Ecay 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 test.org, add the follo

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-16 Thread Andreas Leha
Eric Schulte writes: > Eric S Fraga writes: > >> Eric Schulte 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 blo

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-16 Thread Eric Schulte
Eric S Fraga writes: > Eric Schulte 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 th

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-16 Thread Eric S Fraga
Eric Schulte 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?

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-04 Thread Bastien
Eric Schulte writes: > Done. Thanks! -- Bastien

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-04 Thread Eric Schulte
Bastien writes: > Hi Eric, > > Eric Schulte 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: > > ~$ git clone org...@

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-04 Thread Bastien
Hi Eric, Eric Schulte 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 Otherwise I'll do it my

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-03 Thread Eric Schulte
> > 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 natu

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-04-03 Thread Eric Schulte
Aaron Ecay 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 post-processing of

Re: [O] [RFC] new :post header argument for post-processing of code block results

2013-03-31 Thread Aaron Ecay
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

[O] [RFC] new :post header argument for post-processing of code block results

2013-03-31 Thread Eric Schulte
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 specif