Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!decvax!tektronix!tekcrl!tekgvs!keithe
From: keithe@tekgvs.TEK.COM (Keith Ericson)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: MKS 'mv' (was re: picnix mv)
Keywords: To a non-existent directory---phooom!
Message-ID: <3559@tekgvs.TEK.COM>
Date: 9 Jun 88 21:09:17 GMT
References: <27734@clyde.ATT.COM> <3558@tekgvs.TEK.COM>
Reply-To: keithe@tekgvs.UUCP (Keith Ericson)
Distribution: na
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 40

In article <27734@clyde.ATT.COM> feg@clyde.ATT.COM (Forrest Gehrke) writes:
>The corrected mv command with picnix3 still has a small problem: 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 did this accidentally, misspelling the name of an existent directory.
>The file disappeared.
>
>BTW, the MKS mv command does the same trick.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I could not duplicate the "feat" with MKS mv...

mv complained that the source was not a directory when I did
	mv * alpha
	    or
	mv * ../alpha
(alpha nonexistent in both cases)

It simply moved the file to a new name with

	mv file1 dirname
	    or
	mv file1 ../dirname
(dirname nonexistent in both cases)

And 

	mv file1 c:\foo\bar		 (foo nonesistent)

simply returned with 

	mv: cannot create target file "c:\foo\bar"

Which seems friendly enough for me...

This is with version 2.1d (I think) of the MKS Toolkit.

keith