The backstory
If you saw the presentation that Moa Nandorf and I gave on Sass & Compass at the fall 2011 Drupalcamp Stockholm this past weekend you may remember that we said that one of the major problems when working with Sass instead of plain ol' CSS is that you can't see the line number on which a certain property is set, in Firebug. It turns out that we were wrong. After the session I started thinking on how this problem could be solved and while talking to Fredrik Törnqvist we realized that since sass outputs on which line in the SCSS file every CSS code is generated from, Firebug should be able to parse that and display that instead of which line in the CSS it is from, which is meaningless when working with SASS.
Introducing fireSASS
We weren't the only ones coming to this conclusion. Nathan at nex3 has developed a Firebug plugin named fireSASS using a similar method which makes Firebug display the line number from the SCSS file instead! Not only that, it supports the Textmate, MacVim and Emacs URL Scheme so that you can right-click on the SCSS file link and open it in your editor directly, on that particular line!
Blablabla.. How do I enable it?
Nathan has written an excellent blog post on how it works and how to enable it. We use it together with compass and for all you compass users out there I have attached a compass config file(you will have to rename it to config.rb) file with the neccessary debug_info parameter enabled.
Bonus tip: Open in Sublime Text Editor
If you, like me, use the excellent Sublime text editor 2 and want to open your Sass files in that editor you can use this application to make textmate links open in Sublime instead. It even opens on the correct line!

Comments
Didrik Nordström
December 11, 2011Spännande! Jag skrev om detta för två år sen när jag jobbade på Kodamera, det verktyg som jag använde hette CSScaffold. Antagligen var SASS bättre och tog ledningen. Här är inlägget jag skrev: http://www.kodamera.se/blogg/2009/10/css-steroids
Andreas Sahle
December 11, 2011Thanks for the hint with the sublime handler! Got to give it a try :)
Too bad that there is no chromeSASS…
Anonymous
December 11, 2011The “blog post” link appears to be wrong.
Mattias Hällkvist
December 11, 2011Indeed! It’s fixed now. Thanks for pointing that out!
drupleg
December 11, 2011Thanks for the tip! I just got this working very nicely with the new Sassy module
http://drupal.org/project/sassy
http://drupal.org/node/1348888
tsi
December 11, 2011I invite you guys to try out our brand new 965 theme. we have FireSass support built-in :)
It is still a work in progress but so far we really like it.