9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] v8 shell
Date: Sun, 16 Nov 2003 09:23:31 -0500	[thread overview]
Message-ID: <E1ALNoM-00052N-Ko@t40.swtch.com> (raw)
In-Reply-To: Your message of "Sun, 16 Nov 2003 11:45:35." <2cd42c087fdb421f50167b5b1bc9d4dc@hamnavoe.com>

> > 	tar c . | tee >{wc -c} | @{cd somewhere; tar x}
>
> Wow - I use <{cmd} a lot but I had never realised that >{cmd} works too.
>
> What I do miss in rc (does any other shell do it?) is the ability to
> open a read-write connection to a file.  For example you could test
> webcookies(4) by doing something like:
>
> <>[4]/mnt/webcookies/http { echo http://www.foo.baz >[1=4]; cat <[0=4] }
>
> Because the webcookies protocol requires that you write the url and read back
> the cookies on the same file descriptor, I can't see any way to do this in
> the existing shell.

i put this in byron's rc once but didn't bother
trying to convince anyone it was actually
useful on unix (especially since some more
magic was required to open unix domain
sockets transparently).

for lockstep protocols (one write, one read, ...)
you can use aux/rdwr.

	echo plan9.bell-labs.com mx | aux/rdwr /net/dns

there should be an option to silence the "> " prompts.



  parent reply	other threads:[~2003-11-16 14:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.21.0311131606190.27715-100000@zenon.ceid.upatras.gr>
2003-11-13 16:06 ` Taj Khattra
2003-11-13 17:41   ` rob pike, esq.
2003-11-13 23:44     ` George Michaelson
2003-11-14  0:43       ` rog
2003-11-14  6:59         ` boyd, rounin
2003-11-17 10:26           ` Douglas A. Gwyn
2003-11-17 12:13             ` Charles Forsyth
2003-11-18  9:48               ` Douglas A. Gwyn
2003-11-14 12:04         ` John Murdie
2003-11-14 18:01           ` rog
2003-11-14 19:04             ` boyd, rounin
2003-11-14 19:18               ` rog
2003-11-14 19:31                 ` boyd, rounin
2003-11-14 22:25             ` Roman Shaposhnick
2003-11-16 11:45             ` Richard Miller
2003-11-16 12:01               ` Geoff Collyer
2003-11-16 12:21                 ` Richard Miller
2003-11-17 20:31                   ` rog
2003-11-16 14:23               ` Russ Cox [this message]
2003-11-16 14:35                 ` Richard Miller
2003-11-15 15:03           ` a
     [not found] ` <oprykztjlztsux9g@smtp.borf.com>
2003-11-14  0:41   ` boyd, rounin
2003-11-14 17:51     ` rog
2003-11-14 18:51       ` boyd, rounin
2003-11-17 10:26       ` Douglas A. Gwyn
2003-11-14  7:05   ` boyd, rounin
2003-11-14  8:13 boyd, rounin
2003-11-14 18:12 Richard C Bilson
2003-11-14 19:09 ` rog
2003-11-14 19:12 ` boyd, rounin

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=E1ALNoM-00052N-Ko@t40.swtch.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).