shell() question

David Bovill david at
Thu Jul 23 03:28:47 EDT 2015

Well I found one - though I'm not sure it is strictly legal:

  put "<some text" into $LIVECODEVAR
>   put shell ("echo $LIVECODEVAR | shellThing -q")

which is great. I don't "think" this pollutes the environment, as AFAIK
shell() is in it's own space (like opening a tab in the terminal) - but are
there any issues?

I'd like to try writing to a process - as I think you can do the equivalent
of shell with a commandline tool. Does anyone have an example - and can
explain "elevated" process - the docs are a bit sparse. Is elevated like

On 23 July 2015 at 08:18, David Bovill <david at> wrote:

> I'm wandering if there is a neat trick to pass data to a shell command via
> STDIN. The only thing I know how to do is either:
>    1. Write a bash script that accepts an input param and call this
>    2. put shell ("echo 'some text' | shellThing")
> Is there a neater way?

More information about the Use-livecode mailing list