On Fri, Nov 30, 2018 at 11:25 AM Marcin Borkowski wrote:
> On 2018-11-28, at 03:08, Grant Rettke wrote:
> > On Tue, Nov 27, 2018 at 3:57 AM Marcin Borkowski wrote:
> >> but it's fairly complicated. Any better ideas?
> >
> > What is the part that you think is too complicated?
>
> I hoped that I
On 2018-11-28, at 03:08, Grant Rettke wrote:
> On Tue, Nov 27, 2018 at 3:57 AM Marcin Borkowski wrote:
>> but it's fairly complicated. Any better ideas?
>
> What is the part that you think is too complicated?
I hoped that I could somehow skip the "manually replace newlines with
spaces" step.
On 2018-11-28, at 08:08, Eric S Fraga wrote:
> On Tuesday, 27 Nov 2018 at 19:33, Samuel Wales wrote:
>> this might be the most ridiculous idea you have ever heard, but does
>> babel have a concept similar to stdio pipes? i've often wanted to
>> just pipe stuff. dunno if this would help marcin
On Thursday, 29 Nov 2018 at 15:18, Samuel Wales wrote:
> it still feels like variables to me.
I agree. It's not the *same* as a pipe but does meet some of the requirements
for some use cases... I think expecting behaviour like pipes is possibly too
much given the single threaded nature of mu
On Thursday, 29 Nov 2018 at 15:16, Samuel Wales wrote:
> On 11/28/18, Eric S Fraga wrote:
>> The output (or more generally the results) of one src block is passed
>> directly as input to another using the :post argument.
>
> that helps.
>
> i'm not familiar with many languages. shell and lisp wor
it still feels like variables to me. if you did a shell example with
1000 lines, would those be piped in? or would the variable contain
1000 lines? i don't understandt he difference between post and just a
variable.
onte: i am only telling you this to improve documentation if you feel
like it.
On 11/28/18, Eric S Fraga wrote:
> The output (or more generally the results) of one src block is passed
> directly as input to another using the :post argument.
that helps.
i'm not familiar with many languages. shell and lisp work best for
me, but in this case saying that clarifies.
not sure
On Wednesday, 28 Nov 2018 at 15:35, Samuel Wales wrote:
> fyi only: i don't understand the examples or the relevance to pipes.
The output (or more generally the results) of one src block is passed directly
as input to another using the :post argument.
See, for instance:
#+begin_src org
,#+n
fyi only: i don't understand the examples or the relevance to pipes.
On 11/28/18, Eric S Fraga wrote:
> On Tuesday, 27 Nov 2018 at 19:33, Samuel Wales wrote:
>> this might be the most ridiculous idea you have ever heard, but does
>> babel have a concept similar to stdio pipes? i've often wanted
On Wed, Nov 28, 2018 at 1:08 AM Eric S Fraga wrote:
> Check out the :post option for src blocks. May be exactly what you
> want.
Thanks for sharing that!
On Tuesday, 27 Nov 2018 at 19:33, Samuel Wales wrote:
> this might be the most ridiculous idea you have ever heard, but does
> babel have a concept similar to stdio pipes? i've often wanted to
> just pipe stuff. dunno if this would help marcin.
>
> the only inter-block communication i am aware of
this might be the most ridiculous idea you have ever heard, but does
babel have a concept similar to stdio pipes? i've often wanted to
just pipe stuff. dunno if this would help marcin.
the only inter-block communication i am aware of are variables and
noweb inclusion.
[and, unless i am mistaken
On Tue, Nov 27, 2018 at 3:57 AM Marcin Borkowski wrote:
> but it's fairly complicated. Any better ideas?
What is the part that you think is too complicated?
Hi folks,
I have a multiline source block (a complex sql query). I'd like it to
be inserted into another (shell) source block, so that I can run psql on
a remote server (via ssh) and execute this query (I cannot access the
database from my machine).
I came up with this:
--8<---cut h
14 matches
Mail list logo
