From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] PUSH sources for Plan 9
Date: Sat, 29 Jan 2011 12:31:14 -0800 [thread overview]
Message-ID: <AANLkTi=AYwemQ48_t1tg_6=7-Qh41VBULzj4yR-5Kbx6@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimPxQW_QhhSiJiaaO2tUdcAeM6PthAJnrpyda2M@mail.gmail.com>
Hi Noah,
I pinged you offline. Not sure if you got my
messages.
It seems that your fan-in operator creates
the pipes, then they're passed along to the
ORF and IRF through argv (via the fan-out
and fan-in respectively). I've checked that
indeed the pipes are being created, by
running push -r ... and subsequently
checking /fd to make sure the corresp.
file descriptors are there. And the '-r'
flag even tells me:
...
Xsimple (../fdcat ) (13 9 5 )
...
Xsimple (echo ) (14 10 6 )
...
and yet, my IRF and ORF programs
don't receive any arguments - the argv
list is empty for both. Any ideas why
this could be?
Thanks,
ak
On Thu, Jan 27, 2011 at 2:30 AM, Noah Evans <noah.evans@gmail.com> wrote:
> You need filters and the filters need to be set up by default in
> rcmain. Anthony is on top of things as usual :) It would be nice to
> have other users and if you are interested in exercising it ping me
> offlist.
>
> Noah
>
>
>
> On Thu, Jan 27, 2011 at 10:08 AM, Akshat Kumar
> <akumar@mail.nanosouffle.net> wrote:
>> Is "broken!" the default prompt, or am I
>> seeing some error here? A primitive
>> grep of the source files didn't reveal
>> any instance of that string, so I wonder...
>> Also because:
>>
>> broken! echo hello |< cat >| cat
>> rc (push): empty argument list
>> rc (push): empty argument list
>> term%
>>
>> Perhaps I should try the test/ dir first...
>>
>>
>> Thanks!
>> ak
>>
>> On Wed, Jan 26, 2011 at 7:22 PM, Eric Van Hensbergen <ericvh@gmail.com> wrote:
>>> On Wed, Jan 26, 2011 at 8:52 PM, Akshat Kumar
>>> <akumar@mail.nanosouffle.net> wrote:
>>>> Yes, I've seen this. This is the port to Plan 9 Ports.
>>>> I would like the code for Plan 9. I imagine reproducing
>>>> will make things uglier than the original.
>>>>
>>>> On Wed, Jan 26, 2011 at 5:48 PM, Jacob Todd <jaketodd422@gmail.com> wrote:
>>>>> http://code.google.com/p/push/
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> https://bitbucket.org/ericvh/hare/src/3b24a40eb3d1/sys/src/cmd/push/
>>>
>>> may be partial, development is ongoing - bug noah.
>>>
>>> -eric
>>>
>>>
>>
>>
>
>
next prev parent reply other threads:[~2011-01-29 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 1:42 Akshat Kumar
2011-01-27 1:48 ` Jacob Todd
2011-01-27 2:52 ` Akshat Kumar
2011-01-27 3:22 ` Eric Van Hensbergen
2011-01-27 9:08 ` Akshat Kumar
2011-01-27 9:20 ` Anthony Sorace
2011-01-27 10:30 ` Noah Evans
2011-01-29 20:31 ` Akshat Kumar [this message]
2011-01-29 22:32 ` Noah Evans
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='AANLkTi=AYwemQ48_t1tg_6=7-Qh41VBULzj4yR-5Kbx6@mail.gmail.com' \
--to=akumar@mail.nanosouffle.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).