Tim Douglas

I'd argue this is probably beyond the scope of the plugin, to me it feels like something that would be better achieved with a [grunt](https://github.com/gruntjs/grunt) build step or similar

Hmmm, anything untoward in the sublime python console?

Looks like something funky is being returned from the call to actually compile the Less, but it isn't being caught as intended. Can you try putting in a print after:...

`settings` itself is a key inside `json` object, so you may need to wrap the whole thing in curly braces, eg: ``` { "settings": { "less2css": { ... } }...

Can you paste your stack trace from your sublime console when you save a less file? Also, what platform are you running on?

looks like `main_file` is relative to the current less file being compiled, so you may need to set `main_file: "../main.less"` in your settings file

I should be able to test on ubuntu in the next few days

Looks like it fails on ubuntu 12.04 Tried to save a file called `téstubuntu.less` ``` Traceback (most recent call last): File "./sublime_plugin.py", line 362, in run_ File "./less2css.py", line 45,...

I wouldn't be worried about supporting a feature that only works for one kind of project structure, as we already do with the `auto` and `shadow` settings (in a sense...)....

This is related to #53, if you're not using ubuntu you could try using that branch