Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!tamuts!n138ct From: n138ct@tamuts.tamu.edu (Brent Burton) Newsgroups: comp.sys.mac.misc Subject: Re: System 7.0 vs. NeXT Step Message-ID: <11492@helios.TAMU.EDU> Date: 24 Jan 91 20:37:00 GMT References: <1991Jan23.204448.23778@unx2.ucc.okstate.edu> <5646@idunno.Princeton.EDU> Sender: usenet@helios.TAMU.EDU Followup-To: comp.sys.mac.misc Distribution: comp Organization: Texas A&M University Lines: 32 >Are you proposing that we be able to pipe data from Versaterm to >MacPaint? Now there's an idea I didn't have. On UNIX systems, pipes can contain what character data you want, but typically text information. This really is an interesting idea - the concept of piping RAW INFORMATION to other programs - almost like message passing but programs not only pass a message, they send a book. Being able to pass information be- tween programs and having that information tagged in some way (as to mark it as TEXT, PICT, PostScript, etc.) might be a useful concept for such areas as hypertext (which I am interested in). I might follow this... >Piping is nice when you have small programs whose only function is to >manipulate the data piped into them, and pipe out changed data, such >as grep and colrm and sort. There are no programs like these existing >for the Macintosh, as far as I know. I just responded to a fellow netter about future changes to MacOS. As many of you have seen, I am a 100% pro-UNIX person. I enjoy the power and usefulness of these small utilities and the way you may combine them together to create new 'commands.' I think, besides IPC, the mac world could benefit from some type of piping system. Having a command line on a mac is sacreligious (sp?) almost, but I'm not saying kill off the windows. Just, "in addition to the windows..." +----------------------+------------------------+ | Brent Burton | n138ct@tamuts.tamu.edu | | Computer Sci/Physics +------------------------+ | Texas A&M University | brentb@nuchat.UUCP |