3 ms·

Springy. http://www.springyarchiver.com/ http://www.springyarchiver.com/ An archiver for OS X that actually works the way you expect, by opening a window to le

Springy. http://www.springyarchiver.com/ http://www.springyarchiver.com/ An archiver for OS X that actually works the way you expect, by opening a window to let you look inside and selectively extract from archives, rather than just spurting files all over the place unbidden like the built in one and all the other replacement ones seem to do. For some reason it took me ages to find this when I switched to mac. Drove me mad.

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 ago
  Yes, 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 ago
    As 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 ago
      While 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".

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 ago
Yes, 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 ago
  As 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 ago
    While 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".