Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!pasteur!ucbvax!decwrl!decvax!tektronix!tekcrl!tekgvs!toma
From: toma@tekgvs.TEK.COM (Tom Almy)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: picnix3  mv
Keywords: To a non-existent directory---phooom!
Message-ID: <3563@tekgvs.TEK.COM>
Date: 10 Jun 88 14:25:54 GMT
References: <27734@clyde.ATT.COM> <7449@swan.ulowell.edu>
Reply-To: toma@tekgvs.UUCP (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 19

In article <7449@swan.ulowell.edu> boneill@hawk.ulowell.edu (SoftXc Coordinator) writes:
>In article <27734@clyde.ATT.COM> feg@clyde.ATT.COM (Forrest Gehrke) writes:
>>[...] If you should happen to request a
>>move of a file to a non-existent directory, it
>>"moves" it and deletes it from the source
>>directory---all silently.  
>
>I was unable to recreate this problem. 

Well, I was able.  I  don't use PICNIX mv (I use a MetaWare version), but I
tried it with PICNIX cp, the new "corrected" version:

cp file \foo\bar

where directory \foo does not exist, causes a copy of the file to be made in
the *current* directory, called "foobar".  Not too nice.

Tom Almy
toma@tekgvs.TEK.COM