|
|
Quickly remove resource forks
You can empty the resource fork of a file a_file by doing:
Should be a hint on it's own!
This one is really a hint in it's own right... I had no idea that you could access the resource fork that way!
Should be a hint on it's own!
It turns out Rob already has posted a hint about this here, and there's an interested comment at the bottom about using the '..namedfork' route to get at any named fork.
You're right about there being some overhead with a resource fork. When you 'create' a resource fork with ResEdit, it adds a header to the fork. But every file does automatically have a resource fork that you can read from and write to, it just normally has length 0, i.e. no header info. Michael
yes, this is the preferred way to do it
... since all it changes is the resource fork.. approaches with cp etc. are more cumbersome, and can lose other info that doesn't take extra space or complicate file transfers.. they will even fail under certain circumstances (such as too little space, permissions problems ...)
if you are writing this into a script, or reading this years later, you'll want to use the non-deprecated form "/..namedfork/rsrc".. another way to express this is:
and yes, emptying a resource fork is all that's needed (technically, you can never really delete a resource fork on HFS+) |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.10 seconds |
|