Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!kubix!kub.nl!kolb From: kolb@kub.nl (Hans-Peter Kolb) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: 4dos misfeature? Message-ID: <1991Mar11.103356.17433@kub.nl> Date: 11 Mar 91 10:33:56 GMT References: <1828@manta.NOSC.MIL> <1991Mar7.065400.24641@en.ecn.purdue.edu> <1616@gufalet.let.rug.nl> Reply-To: kolb@kub.nl (Hans-Peter Kolb) Organization: Tilburg University, Tilburg, The Netherlands Lines: 28 In article <1616@gufalet.let.rug.nl>, dboer@let.rug.nl (A. de Boer) writes: |> I seem to remember that in the header of the documentation it says |> that MOVE is designed to move files either to other directories or to |> other drives. This should cancel any suggestions that may be made by |> the ensuing documentation as to MOVE's capability of functioning as a |> kind of RENAME. Its not being able to do so follows from its |> definition From the 4dos documentation: Syntax: MOVE [/PQR] [d:][path]filename... [d:][path]filename ^ ^^ ^^^^^^^^^ Let's call a bug a bug --- even if we like the program that exhibits it. Moving a file within a directory (i.e. renaming) is just a special case of moving it across directories/drives. The []'s around "d:" and "path" above show that the 4dos designers are of the same opinion. So if using move as a sort of rename confuses 4dos or---even worse---scrambles disks, THIS IS A BUG and has to be fixed! Best, ...hap ------------------------------------------------------------------------ hans-peter kolb kolb@kub.nl Computational Linguistics kolb@htikub5.bitnet Tilburg University (KUB) P.O.Box 90 153 The Netherlands NL-5000 LE Tilburg ------------------------------------------------------------------------