From: "peter a. cejchan" <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: [9fans] Re: \n\n\n to \n\n
Date: Thu, 6 Mar 2003 07:25:42 +0100 [thread overview]
Message-ID: <000801c2e3a9$36cf2b00$2a8be793@gli.cas.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
>> I just wonder why Edit is a built-in... I would prefer piping to (streamed) sam...
>> wouldn't that be a cleaner solution?
> First, there isn't a streamed sam, and second, streaming only works
> for one file. Second, you *can* stream text through commands; I do it
> all the time. (|fmt, |sort, |tr A-Z a-z, etc. etc.)
So do I. I was just curious why there is a built-in Edit instead of having "a better sed" ... I thought of Acme
as of an environment (say, glue), not a text teditor. Would love to have Plan 9 like a "LEGO" (TM), and more: single
piece for every "task".... maybe stupid, but I would love sed with capabilities of Edit...
PS: I'm going to test the posted wrappers to Sam, and then, hopefully, forget of Edit, and |sed ;-)
++pac
[-- Attachment #2: Type: text/html, Size: 1474 bytes --]
next reply other threads:[~2003-03-06 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 6:25 peter a. cejchan [this message]
2003-03-07 11:14 ` Douglas A. Gwyn
2003-03-07 12:34 ` Fco.J.Ballesteros
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 18:05 rog
2003-03-05 15:12 peter a. cejchan
2003-03-05 19:20 ` Fco.J.Ballesteros
2003-03-05 6:52 peter a. cejchan
2003-03-05 17:26 ` rob pike, esq.
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='000801c2e3a9$36cf2b00$2a8be793@gli.cas.cz' \
--to=cej@gli.cas.cz \
--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).