> On Sep 20, 2021, at 20:41, Mia Burger <mia.bur...@gmx.de> wrote:
>
> Hello,
>
> I created a small example in today's post:
>
> https://picolisp-blog.hashnode.dev/picolisp-explored-piping-from-the-command-line
>
> Hope it helps!
Excellent :-)
That: in <list> is pretty much like
do shell script "..." in Applescript
(in '("upower" "-i" "/org/freedesktop/UPower/devices/battery_BAT1") (prinl
(line)))
do shell script "upower -i /org/freedesktop/UPower/devices/battery_BAT1"
And the piping solution is much clearer now.
Thank you so much, and Alex too.
Jean-Christophe
> Am 19.09.21 um 17:32 schrieb Alexander Burger:
>> Hi Jean-Christophe,
>>
>>> I won't be able to attend (UTC+9...) but I had a question *especially*
>>> after reading Mia's blog.
>>>
>>> How is it possible to "pipe" data to a pil script ?
>>>
>>> Something like
>>>
>>> myOtherScript's result | mypilscript.l
>> This is not difficult. Just keep in mind that due to the REPL-nature of
>> PicoLisp
>> the current input channel is on the script while it is 'load'ed.
>>
>> So you need to redirect the input channel to stdin
>>
>> (in NIL
>> ...
>> (line) # or (read), (char) etc.
>> ... )
>>
>> ☺/ A!ex
>>
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
