4 ms·
The built one doesn't spurt anything: if the archive contains a directory or a single file it extracts that in place, if it contains a bunch of files it will cr
by falling 15y ago
The built one doesn't spurt anything: if the archive contains a directory or a single file it extracts that in place, if it contains a bunch of files it will create a directory with the archive name and put the files in there. This is what I want 99% of the time.
- JonnieCache 15y agoYes, but what if I want one file deeply nested inside a massive archive, like a source tree or something? In the scenario you describe, I generally use the dtrx script. http://brettcsmith.org/2007/dtrx/ http://brettcsmith.org/2007/dtrx/
- falling 15y agoAs I said: 99%. I like default tools to be optimized for the common case, corner cases are just corner cases – how often are you extracting a single file from a massive source tree?
- xoreax 15y agoWhile I agree that for the average user the default behavior is appropriate, there is still room for improvement. I use Entropy ( http://www.EntropyApp.com http://www.EntropyApp.com ) , which is similar to Springy but also includes "in-archive quick look" and mode shortcuts. So, my workflow is now similar to this: 1. By default, automatically extract like the built-in archiver 2. For "transient archives" where I just want to preview the contents (pictures/documents/crash-logs), open with the CMD key pressed to view the contents. Then press space to preview the files. I find myself in situation #2 often enough to warrant something like this. It's a lot more convenient than "Extract all -> navigate -> preview -> move to trash".