atom-csscomb Project csscomb config file should take precedence

A project specific config file should be used in favour of the global one, not the other way around.

Mar 25 '14 19:03 danielchatfield

Ok, I'll buy that -- my original thought was that the specific config file was the user's configuration file -- so should trump any shared (team) configuration, but I can see how this would be problematic across teams (eg, I agree with one, disagree with another). I'll switch the logic and be open to a second, specific "use my config" sort if it's asked for.

Mar 26 '14 00:03 bruce

I agree with Daniel and would prefer this behaviour.

Aug 19 '14 12:08 EmmaStott

:+1: - Is this so difficult that it is not solved yet?

Jun 29 '16 21:06 rugk

@rugk It's likely not all that difficult. However, as I don't use Atom anymore, I'd love it if someone else maintained this project so it can get the attention it deserves. If you're volunteering, fork it and I'd be happy to pass it on.

Jul 01 '16 02:07 bruce

There is no need for this. There are already many alternatives, e.g. https://github.com/jchouse/csscomb-atom

So basically I would however still have a request: Could you please add a note to the Readme saying you abandoned this project? (Maybe linking to an alternative)

And - if possible - can you delete it with apm from the Atom package list?

Jul 01 '16 08:07 rugk