From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] rc of Unix
Date: Sat, 5 Jul 2003 16:00:36 +0200 [thread overview]
Message-ID: <002701c342fd$cf627080$d2944251@insultant.net> (raw)
In-Reply-To: <6496F535-AEE2-11D7-B36C-000393A941BC@ar.aichi-u.ac.jp>
i used rc on ultrix for 2+ years and i never really ran into a problem.
yes, sed 1q is different to to plan 9's read 'cos sed 1q discards
the whole input stream whereas read just takes the first line
(preserving the the rest of the input stream).
i don't remember how i avoided this problem, but it probably
involved pipe trickery and awk. it depends on the problem.
next prev parent reply other threads:[~2003-07-05 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 2:17 Kenji Arisawa
2003-07-05 2:33 ` Bruce Ellis
2003-07-05 12:15 ` Kenji Arisawa
2003-07-05 14:00 ` boyd, rounin [this message]
2003-07-05 17:45 David Presotto
2003-07-05 23:20 ` Kenji Arisawa
2003-07-05 23:48 ` rob pike, esq.
2003-07-06 3:19 ` 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='002701c342fd$cf627080$d2944251@insultant.net' \
--to=boyd@insultant.net \
--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).