Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-sdd!ncr-sd!tw-rnd!johnl From: johnl@tw-rnd.SanDiego.NCR.COM (John Lindwall) Newsgroups: comp.sys.amiga.tech Subject: Re: more 1.4 command wishlist Message-ID: <479@tw-rnd.SanDiego.NCR.COM> Date: 9 Aug 89 22:53:54 GMT References: <1989Aug8.214011.3351@agate.berkeley.edu> Reply-To: johnl@tw-rnd.SanDiego.NCR.COM (John Lindwall) Organization: NCR Distributed Systems Laboratory Lines: 45 In article <1989Aug8.214011.3351@agate.berkeley.edu> mwm@mica.berkeley.edu (Mike (I'll think of something yet) Meyer) writes: > > >Simple example: It'd be nice if stack's output was "stack" >instead of "Current stack size is " - or that you could make it >do that. Why? How about a script like: > >stack >ram:resetstack >stack 50000 >; run some thing that needs 50K of stack >execute ram:resetstack > > [Other examples deleted] My first reaction was one of agreement. Assuming Arexx is part of the 1.4 release, though, means we could use its extensive string handling capabilities to handle these verbose outputs. It would also cool to have invocation of Arexx scripts without prepending 'rx', just like with 1.3 we can run scripts without prepending 'execute' to the command line. Perhaps the same mechanism that WShell uses could be employed (or maybe a Rexx protection bit --- UG- forget I said that!). >Once again, it'd be nice if the output from all commands was examined, >and changed (or flags added to make it change) to something more >suitable for feeding to other commands (including execute). > >