Path: utzoo!attcan!uunet!van-bc! From: lphillips@lpami.wimsey.bc.ca (Larry Phillips) Newsgroups: comp.sys.amiga Subject: Re: cp-mv-rm1.1 command substitute Message-ID: <1837@lpami.wimsey.bc.ca> Date: 1 Aug 90 20:51:49 GMT Lines: 30 Return-Path: To: van-bc!rnews In , hclausen@adspdk.CBMNET (Henrik Clausen) writes: >>In article <2666@mindlink.UUCP> a218@mindlink.UUCP (Charlie Gibbs) writes: >> No, I don't. The main reason I stick with Matt Dillon's Shell2.07m >>is that its cp command assumes CLONE by default. I'm a date-stamp >>fanatic; I depend on them for program version control, and so does make. >>Perhaps the best solution would be to have an environment variable to >>determine the default action of any copy (are you listening, Commodore?). > > I'm a date-stamp fanatic, too, so I've put the following into my >Shell-Startup file: > >Alias cp "copy clone " > > Simple, eh? Yes, and also a kludge that should not have to be done. Bottom line is that it doesn't necessarily work for all shells, doesn't come into play when another program calls 'copy', and is not something that everyone knows about or will do. That means that it can't be counted on. It makes file dates and comments useless to have the default behaviour the way it is. -larry -- Sex is better than logic, but I can't prove it. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+