Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu From: lshaw@ccwf.cc.utexas.edu (logan shaw) Newsgroups: comp.sys.amiga.graphics Subject: Re: CLI features Message-ID: <48144@ut-emx.uucp> Date: 30 Apr 91 07:21:44 GMT References: <1991Apr11.153537.4257@cs.UAlberta.CA> <20897@cbmvax.commodore.com> <91119.163516UH2@psuvm.psu.edu> Sender: root@ut-emx.uucp Reply-To: lshaw@ccwf.cc.utexas.edu (logan shaw) Followup-To: comp.sys.amiga.programmer Organization: The University of Texas at Austin Lines: 33 [ note: I changed the followup-to line to comp.sys.amiga.programmer. ] In article <91119.163516UH2@psuvm.psu.edu> UH2@psuvm.psu.edu (Lee Sailer) writes: >Really? Hooray! Hooray! Will you be able to add the "background >operator" at the end of the line, too? As in > >$ command -x -y -z foo bar & > >Instead of > >> run command ..... Not with the standard CLI, I don't think. The annoying thing about it is that although 1.Ram Disk:> list ram:* will work, 1.Ram Disk:> list * still tries to list stdin. And, there aren't unnamed pipes as far as I know (i.e. you can't say "list | more"). Maybe somebody out there will write a shell that implements &, |, *, and filename completion (all optionally to maintain compatibility). -Logan -- // # "He said that He had your number; you cut the telephone line. \X/ # You said you needed a reason; He said 'there ain't much time.' Logan # You kept trying to avoid it; He kept knocking on the door. Shaw # In a flash it was over; you were a prisoner of war." -Rez Band