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.
The standard argument would be to copy the item to some windows box
or data fork only file system and then back to the Mac. Everything
should just work and in the same state as before... So, the same
argument could apply here... that the custom icon would not survive
the foreign copy, a round trip back to the Mac. Now, how often does
this happen in the world depends on who you talk and their
environments... and how big a deal is that? (the guy could be
loosing his one and only fancy icon, hmm...)
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.
alright... I will do that tonite...
pete
_______________________________________________
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
