Author: Vibin

If you’ve been using Mac since a long time, you must have encountered ‘.DS_Store’ files sometime. These are hidden files which get created in Finder automatically, and you can find them in almost every folder on your Mac!

A ‘.DS_Store’ file contains preferences related to the folder and contains information like position of icons, view settings and etc. meta data. All this sounds fine, but if you’re a developer, you’ll surely hate this as these files get into your project folder.

Here’s how you can get rid of these hidden files.

There’s a tool called Asepsis, which does this. Asepsis creates a wrapper around Apple’s framework DesktopServicesPriv which is responsible for creation of .DS_Store files. This wrapper will redirect all the .DS_Store files into a single folder. The exact path of this folder is /usr/local/.dscage.

Asepsis is available as a .mpkg file, so you’ve to install it manually. You’ve to restart your Mac to complete installation and Asepsis will start to run in background. So the next time a .DS_Store file gets created, it goes into the .dscage folder (which is where all .DS_Store files reside).

But Asepsis itself won’t migrate the existing .DS_Store files. For that, you have to fire up terminal and run its command line utility.

Running asepsisctl migratein will migrate all the .DS_Store files from your home directory to .dscage folder. But that’s not all! If you have websites in your /Applications, like me, you have to run asepsisctl --root /Applications migratein. This is because I have my WordPress site under MAMP which is in /Applications/ (and I obviously don’t want .DS_Store files in my site folder).

After you’ve done all this, you can check if .DS_Store files exist in a folder, by running –
find . -iname .ds_store.

One important thing to note is, Asepsis won’t work on Mavericks and you might even run into booting issues if you try to install it.

Thanks to Rakshit Thakker for the geeky tip!

Link: Asepsis

If you’re a developer and use a Unix-like OS, you must be spending a good amount of time inside the shell. Here’s a nice, little tip on how to play Music with in the command line interface, in OS X.

OS X ships with a CLI utility called afplay. There’s not much documentation available, even the man page doesn’t show its options. But it’s there and more importantly, it works.

To use it, pass a Music file’s path in the command, like this:

afplay ~/Music/song.mp3

I guess it works for all Music files, regardless of the type (I tried it with .m4a and it worked fine). To stop the play, you can of course hit Ctrl + C and the shell will terminate it.
You can also play Music in background by appending an ampersand to the command, like this:

afplay ~/Music/song.mp3 &

This will allow you to use the shell while the Music is playing in background. To stop it, you can do killall afplay.

You can also use Quicklook’s CLI to play Music files. The utility is named qlmanage. It basically throws a Quicklook pop up of any file you pass as an argument. So it works fine for Music files too.

If you like this, you might want to take a look at some useful Quicklook plugins. Also, thanks to Rakshit Thakker for the tip!