From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: \n\n\n to \n\n
Date: Wed, 5 Mar 2003 09:26:26 -0800 [thread overview]
Message-ID: <64f5b14c528bef319ba1386d8850a473@mightycheese.com> (raw)
In-Reply-To: <002001c2e2e3$d0f0f0e0$2a8be793@gli.cas.cz>
> 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.)
But to answer your question: I find the X command extremely powerful,
and can't see any way to have a streaming implementation that will
look at multiple files simultaneously.
One day I realized I could easily implement Edit as a command in acme,
but that after about fifteen years of desultory thought I still didn't
see the right way to build a stream sam. The X command was the
clincher, and I started hacking.
-rob
next prev parent reply other threads:[~2003-03-05 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 6:52 peter a. cejchan
2003-03-05 17:26 ` rob pike, esq. [this message]
2003-03-05 15:12 peter a. cejchan
2003-03-05 19:20 ` Fco.J.Ballesteros
2003-03-05 18:05 rog
2003-03-06 6:25 peter a. cejchan
2003-03-07 11:14 ` Douglas A. Gwyn
2003-03-07 12:34 ` Fco.J.Ballesteros
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=64f5b14c528bef319ba1386d8850a473@mightycheese.com \
--to=rob@mightycheese.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).