Comments on: Exclude Compressed CSS from Sublime Text 2 Projects

By: David

David — Mon, 08 Oct 2012 08:33:28 +0000

Wow, awesome. Now I don’t have to distinguish them from my .less files. Thanks!

By: Chris Coyier

Chris Coyier — Mon, 17 Sep 2012 16:05:08 +0000

Yeah totally, that’s what I’m doing now. I also just had Compass start watching one folder level higher so I was able to use it at the theme folder level.

By: James

James — Mon, 17 Sep 2012 06:53:06 +0000

Hey Chris,

There is no need to have that additional HTTP request for wordpress.

Simply use a loud comment in sass.

/*! This will not be removed, so you can put your theme contents in there*/

I blogged a bit more about that here:
http://jamesnowland.com/notes/wordpress-themes-in-sass-scss/

By: Colin Jack

Colin Jack — Wed, 22 Aug 2012 13:05:57 +0000

I do the same myself but I do wish they added a way to exclude folders but only from searches. I do actually sometimes want to dig into the compiled CSS/JS and having to leave Sublime to do it is a bit of a pain.

By: aliweb

aliweb — Wed, 22 Aug 2012 09:15:02 +0000

thanks a lot!
most of your website posts and tips are really tricky and of course , charming!

By: Mike

Mike — Tue, 21 Aug 2012 17:12:49 +0000

Hi Chris, thanks for this. I noticed your screenshot has chrome like tabs. Do you know what app allows this as I’m forever switching windows!

By: Cozy Vision Technologies

Cozy Vision Technologies — Tue, 21 Aug 2012 09:46:32 +0000

Thanks for the tip,

By: Tom Davies

Tom Davies — Mon, 20 Aug 2012 17:44:10 +0000

So I totally get why you might want to do this, but before you follow suit here’s something you should really think about:

If you’re using a CSS preprocessor, you really ought to get into the habit of regularly looking at the compiled CSS that your SASS/LESS/whatever is outputting, in order to check that it’s sane.

It’s way too easy, especially when you’re starting out with preprocessors, to end up generating seriously non-optimal CSS. The classic would be over using nesting, but apparently harmless things like @extending classes that also contain @extends themselves can quickly lead to bloated rules that aren’t actually needed.

Preprocessors are awesome, but with great power comes great responsibility. The compiled CSS is what’s actually delivered to the browser, therefore it’s part of our jobs as a developer to ensure that it’s fit for purpose (ie as lean as possible).

Also, if you’re outputting super-compressed, production-ready compiled CSS in development, you’re gonna have a heck of a time debugging it. Better by far to go with the verbose, line-number-comment laden output for development, then compress/re-compile automatically as part of your build/deploy process.

You do, however, almost certainly want to ignore your sass-cache/ directory, and the .scssc files within it, as these really are annoying when you’re searching in ST2.

By: Balazs Sziklai

Balazs Sziklai — Mon, 20 Aug 2012 09:58:27 +0000

A bit off but as long as we talking about projects in ST2 , check out Bit101`s plugin, for making custom project templates with dynamic assets:

https://github.com/bit101/STProjectMaker

By: yez

yez — Mon, 20 Aug 2012 08:10:18 +0000

Great tip Chris. It’s also pretty handy to exclude framework files you’re not going to touch.
Btw you forgot a “not” in the opening sentence “If you’re using Sublime Text 2″ .

Cheers