Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: PIPEs Message-ID: <7079@sugar.hackercorp.com> Date: 19 Nov 90 00:39:16 GMT References: <1990Nov10.082242.22949@agate.berkeley.edu> <8283@gollum.twg.com> <1990Nov17.072551.5612@agate.berkeley.edu> <1990Nov18.141954.15308@zorch.SF-Bay.ORG> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 20 Another alternative, ksh syntax. This one requres *named* pipes! mkarcv file $(search "pattern" @(list lformat="%s%s" directory)) all Where the commands are run concurrently and the name or contents of a generated file is inserted where the @(...) or $(...) was. This would do effectively: run list >pipe:temp0001 lformat="%s%s" directory run search >pipe:temp0002 "pattern" pipe:temp0001 mkarcv file (contents of pipe:temp0002 inserted in the line here) So $(...) is (as in ksh) equivalent to the UNIX shell syntax `...`, and the @(...) means (insert pipe name here). The biggest advantage here is that existing Amiga commands will work well without being turned into filters. -- Peter da Silva. `-_-' .