Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!gatech!mcnc!ece-csc!rss From: rss@ece-csc.UUCP (Ralph Scherp) Newsgroups: comp.sys.amiga Subject: Bug in ARP Rename command Message-ID: <3579@ece-csc.UUCP> Date: 13 May 88 03:08:32 GMT Reply-To: rss@ece-csc.UUCP Organization: North Carolina State University, Raleigh, NC Lines: 33 I've found what appears to be a bug with the ARP "rename" command. Specifically, if you do a "rename" command with the destination file being a directory of the form "/" or "", the file actually gets put into the directory which is the PARENT of the proper destination directory. E.G.: cd dh0:source/junk rename fubar / gives you the file "dh0:fubar" instead of "dh0:source/fubar"; likewise: rename fubar "" gives you "dh0:source/fubar". If "fubar" instead lives in "dh0:source"; then the sequence cd dh0:source rename fubar / gives you the error message "Can't rename fubar as //fubar", which seems like a strong hint that "rename" is trying to add an inappropriate "/" character before invoking the system (DOS) Rename() function (or whatever the appropriate system call is.) Incidentally, if `rename fubar ""' seems strange, consider going to a subdirectory and doing `rename :fubar ""' to move something from the root of the disk into the current directory, which displays the same behavior. This is with ARP version 34.1 [Is there a later version?]. --Mark Lanzo-- (borrowing a friend's acct)