
I should have written about this months ago. Readers have replied to my previous post about nautilus svn, which I claimed to be the first that didn’t suck. This is the evolution of it, RabbitVCS (Version Control System), which aims to use the same intuitive, integrated gui for other version control systems, such as git (check the rabbitvcs roadmap for details on expected support for different versioning system.

credit to rabbitvcs for the screenshot

Intro
Previously, I had written about enqueuing files with nautilus scripts. Since then, I have learned (and forgotten about) nautilus-actions. Which is a similar way to attack the issue but it using a more intuitive and decoration approach, as well as having the ability to be on the first level of the context menu hierarchy.
sudo apt-get install nautilus-actions
nautilus-actions-config
The approach to getting the example of enqueuing files to mocp accomplished is a bit different using this approach as you don’t need to go through the script as you did before (though you can if you want, it’s an unnecessary step). Here, as my screenshot shows, I directly call mocp from /usr/bin with the -a flag and use the $M variable the legend provided me with to pass a list of files and their full paths to mocp.

You’ll also want to change the conditions on the Conditions tab. I set it to allow multiple files from both folders and files. The default is to allow only a single file.

More
This article was inspired by Making Life Easier With Scripts For Nautilus. If you’re interested in this article, you’ll probably also like my article about nautilus packages you wish were installed by default in ubuntu.