9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] watching plumber
Date: Sat, 13 Mar 2010 18:05:35 -0500	[thread overview]
Message-ID: <3bb7faea1a0f63a0b8694d28d5f706b2@ladd.quanstro.net> (raw)
In-Reply-To: <a560a5d01003131118t206cc37bhbead99701bb6ccf6@mail.gmail.com>

> 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



  reply	other threads:[~2010-03-13 23:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 23:25 Rudolf Sykora
2010-03-12 23:54 ` erik quanstrom
2010-03-13  0:16   ` Rudolf Sykora
2010-03-13  0:39     ` erik quanstrom
2010-03-13  8:19       ` Rudolf Sykora
2010-03-13 10:45 ` Rudolf Sykora
2010-03-13 15:31   ` erik quanstrom
2010-03-13 17:14     ` Rudolf Sykora
2010-03-13 19:18       ` Rudolf Sykora
2010-03-13 23:05         ` erik quanstrom [this message]
2010-03-14 15:55           ` Rudolf Sykora
2010-03-14 20:11             ` erik quanstrom
2010-03-15  4:53               ` Anthony Sorace
2010-03-18 15:34                 ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3bb7faea1a0f63a0b8694d28d5f706b2@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).