> This didn't work, the editor again tried to open the $data file, so I
> deduced 'plumb to edit' can't have additional parameters... (right?)
> ... and tried
>
> plumb start echo $data | plumb -i -d edit -a action=showdata
>
> which, however, does seemingly nothing... I don't understand why...
because the arguments to start are not a shell script, they are a command
plus arguments. in this case you are running /bin/echo with arguments
$data '|' plumb -i -d edit -a 'action=showdata'
i think what you intend to write is more like
plumb start rc -c 'echo '$data' | plumb -i -d edit -a
''action=showdata'''
with a little bit of hindsight, perhaps it might have been easier for
the plumber to make the arguments a shell script and feed the literal text
to the shell.
in any event, that's not what we've got. and you can easily get around
this by writing a shell script that keeps the complication out of the
plumber's rules.
- erik
