Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!sdcsvax!ucbvax!YALE.ARPA!ram-ashwin
From: ram-ashwin@YALE.ARPA (Ashwin Ram)
Newsgroups: comp.sys.apollo
Subject: Re: Why Aegis looks like Unix.
Message-ID: <8706091401.AA07693@yale-celray.arpa>
Date: Tue, 9-Jun-87 10:01:52 EDT
Article-I.D.: yale-cel.8706091401.AA07693
Posted: Tue Jun  9 10:01:52 1987
Date-Received: Fri, 12-Jun-87 02:40:38 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 24

>          mv		vs.	???		moving and renaming files
>
>  ??? = chn (change name, applicable directories or files).

Actually, MV corresponds to MVF (move file).  As far as I can see, CHN is
functionally a subset of MVF.  Couple things that are inconsistent in this
setup: 1, CHN doesn't accept the standard -R (replace) or -CHN (change
name) flags that MVF and CPF do, with the result that you often have to use
MVF anyway after CHN fails.  2, You use CPF to copy a file and CPT to copy a
tree, but you use MVF to move both files and trees/directories (unless you
specify a wildcarded name, in which case MVF moves the files that it matches
but not the trees).  Weird.

Aside:
One nice feature of Aegis wildcards that I swear by: the "..."  specification
that matches zero or more nested directories.  One nice feature of Unix
filespecs that Aegis would do well to adopt:  the "~user" specification to
refer to a user's home directory.  Very useful in a cooperative environment.

-- Ashwin Ram --

ARPA:    Ram-Ashwin@yale
UUCP:    {decvax,linus,seismo}!yale!Ram-Ashwin
BITNET:  Ram@yalecs