Ah... That's an interesting use of ls... And you and Larry are
right... I almost forgot there's the resource fork that could exist
in a file... Just a bit surprised that after all the preaching not
to use the resource fork, yet Finder still uses it... Can't blame
others now, can we? :-)
Arguments against using resource forks in certain contexts are
sensible, but in the case of custom icons I don't personally see much
motivation to change the established practice.
Note that in Tiger 'cp' now copies resource forks from the command line.
So, is this a known issue in Finder? Why can't Finder removed that
Icon^M file when the custom icon is removed, other than a bug?
There *is* other data that the system can store in that fork, but I
can't think of any reason it would need to stay around if the icon
resource being removed was the last one (and the data fork is also
empty). Currently there is no attempt to remove the file.
I looked in Radar and couldn't find anything relevant, so feel free
to file a bug.
Cheers,
--Dave (aka email@hidden)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
