From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Input/output
Date: Thu, 3 Dec 2009 10:27:58 -0800 [thread overview]
Message-ID: <dd6fe68a0912031027v1ac0398fvbd60862f45c4aff3@mail.gmail.com> (raw)
In-Reply-To: <hf8tg7$hed$1@ger.gmane.org>
2009/12/3 Maurício CA <mauricio.antunes@gmail.com>:
> I would like to write a script that takes text from standard
> input, lets the user edit it with 'sam -d' and then prints it to
> standard output.
http://bitbucket.org/rsc/plan9port/src/tip/bin/ssam
next prev parent reply other threads:[~2009-12-03 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 17:45 Maurício CA
2009-12-03 18:27 ` Russ Cox [this message]
[not found] <<hf8tg7$hed$1@ger.gmane.org>
2009-12-03 19:34 ` erik quanstrom
2009-12-04 13:13 ` Maurício CA
2009-12-04 18:51 ` Russ Cox
2009-12-04 22:44 ` Maurício CA
2009-12-05 1:45 ` Jorden Mauro
[not found] <<3aaafc130912041745ub300dc6w498ddedfea62d837@mail.gmail.com>
2009-12-05 1:53 ` erik quanstrom
2009-12-05 4:16 ` Jorden Mauro
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=dd6fe68a0912031027v1ac0398fvbd60862f45c4aff3@mail.gmail.com \
--to=rsc@swtch.com \
--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).