I don't understand why you need options at all... If you point it at a file/directory it should automatically compress and if you point it at an archive it should automatically decompress. The options should be there for advanced tasks not 90% of the tasks you need the app for. It's really poor ui design.
Lately, all of my tar use has been `tar -xvf filename`. I don't remember it always being the case that those options would automatically gunzip/uncompress, but they do now!
Hm, what OS? They didn't in the past. You needed to use 'tar -zxvf' for gunzip and 'tar -jxvf' for bzip2 IIRC. I still use it today to wrap files and move them on my server. On the server I use 'lzma' as default compression for archiving files (sql schemas, conf files, etc.)
Primarily Ubuntu, I'm not sure if this worked on my laptop when I was using Arch a couple years ago... I'd estimate the behavior has been around since 2008-2009.
I've found the option[1], but it's not in my alias list.
Edit: Changelog says Version 1.20 (2008-04-14) introduced the --auto-compress option
The article, and other comments in this thread (mentioning "baseband" etc.) suggest that encryption on the phone can not possibly work.
Closed-source code on a lower abstraction level could read the plaintext I type on the keyboard before it reaches your app. That code can apparently also "phone home" on its own term.
In spite of the fact that Ruby is indeed standard on Mac OS X, a simple shell script would have been clearly lighter. However, for proper JSON escaping of the snippet, you need a full set of replacing rules, which kind of kills the purpose. So I give up.
Increase or decrease volume by small increments: alt + shift + volume up / volume down or brightness up / brightness down.
Also Alfred and Shortcat app.
