rap@ardent.UUCP (Rob Peck) (03/16/88)
I have found a reason to keep my AmigaDOS copy command on the WB, with
the ARP equivalent renamed to: cp
My very favorite way of creating a short and sweet file for execute
script testing (or AREXX script testing) is:
copy * to ram:test
and under ARP, this just returns to the prompt immediately. Under
AmigaDOS copy, the "*" is taken to be the file handle of the console
device, allowing me to redirect what I type at the console to a file.
I missed it enough that I now keep both versions of copy handy, one
renamed as indicated.
===================== begin separate topic =========================
Request::: to the SHELL creators - I'd like to see (and use) Unix's
'script' capability on the Amiga. For those of you not familiar
with it:
script filename
creates a new instance of a shell, running on top of the old shell,
and records everything that appears in the subshell's window. When
you type:
exit
the system says:
Script ended, file name is 'filename'
Sometimes I put together a long compile and walk away - if I am not
piping the output thru the equivalent of 'more', (does stderr accept piping?),
I lose the scrolloffs. Script, under Unix, captures stdout and stderr
to a file and I find that quite useful at times.
Just a thought.
Rob Peck ...ihnp4!hplabs!ardent!rapcmcmanis%pepper@Sun.COM (Chuck McManis) (03/17/88)
In article <329@ardent.UUCP> rap@ardent.UUCP (Rob Peck) writes:
->My very favorite way of creating a short and sweet file for execute
->script testing (or AREXX script testing) is:
->
-> copy * to ram:test
->
->and under ARP, this just returns to the prompt immediately. Under
->AmigaDOS copy, the "*" is taken to be the file handle of the console
->device, allowing me to redirect what I type at the console to a file.
->I missed it enough that I now keep both versions of copy handy, one
->renamed as indicated.
You can do this with the arp copy command using
copy to ram:test
as equivalent syntax.
--Chuck McManis
uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.langz@athena.mit.edu (Lang Zerner) (03/17/88)
In article <45772@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes: :In article <329@ardent.UUCP> rap@ardent.UUCP (Rob Peck) writes: :->My very favorite way of creating a short and sweet file for execute :->script testing (or AREXX script testing) is: :-> :-> copy * to ram:test :-> [...ARP copy uses * for a wild card, so I keep both copy programs :-> available, the ARP rcopy renamed to cp.] : :You can do this with the arp copy command using : copy to ram:test :as equivalent syntax. There is also the very convenient and quite tiny 'input' program which I believe is included on the ARP 1.04 distribution. The equivalent command would be simply 'input ram:test'. Be seeing you... --Lang Zerner langz@athena.mit.edu ihnp4!mit-eddie!athena.mit.edu!langz "To be clever enough to get a great deal of money, one must first be stupid enough to want it." -- G.K. Chesterson
page@swan.ulowell.edu (Bob Page) (03/17/88)
rap@ardent.UUCP (Rob Peck) wrote: > copy * to ram:test >under ARP, this just returns to the prompt immediately. My understanding is that ARP has an environment variable you can set to use either unix/ms-dos wildcards or amigados wildcards. ..Bob -- Bob Page, U of Lowell CS Dept. page@swan.ulowell.edu ulowell!page "Why? It's the heat." -- Laurie Anderson