Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!mcsun!hp4nl!eutrc3!rcbaem
From: rcbaem@eutrc3.urc.tue.nl (Ernst Mulder)
Newsgroups: comp.sys.mac
Subject: FINDER BUG?!?! :)
Message-ID: <885@eutrc3.urc.tue.nl>
Date: 4 Sep 89 07:40:40 GMT
Reply-To: rcbaem@eutrc3.uucp
Organization: Eindhoven University of Technology, The Netherlands
Lines: 37


 At last, I found a nasty little bug in the Finder, try the following:

1) Pick any file and remember its name.
2) Create a new folder and put the file in it.
3) Give the folder the same name as the file has. (You DID remember it, did
   you?)

 So now you have a folder with a file in it with the same name. I was in
this situation, and had to move the file out of the folder. Dropping it next
to the folder won't work, you get a message 'files can not be replaced by
folders and vice versa'. Being a Lasy Mac User I didn't want to use my
keyboard, my other hand was busy holding a sigarette anyway. So I thought
I was clever and did the following:

4) Throw the folder with the file in it in the Trash.
5) Open the Trash.
6) Open the folder in it.
7) Move the file from the folder onto the disk it came from.

'Oops'... :) See the rest for yourself. I tried it a couple of times, even
from a fresh system, With System 6.0 and 5.0, it just won't work.

 I think the following is the cause. When there's something in the trash
having the same name as something on the disk, the trashed file is deleted.
(Duplicate any file, throw away the original and rename the Copy of.. to the
original name. The trash gets emptied).
 I think the finder doesn't like to copy a file which parent directory got
erased during the copy.. (The mere thought gives an ID=02 :)

 Maybe Apple should invent an error Alert for this situation. (I only found
the bug after 3 years of Mac usage.)

 StopAlert():  'Well you should use your keyboard for once, smart-ass!'

 Ernst.
   >