somefile.sass # gets compiled to somefile.css _somefile.sass # does not get compiled, which makes it useful for importing settings.
The import call in your other sass files stay the same. There's no way to "extract" the variables and mixins from a file with rules in it as well. If that's what you're after, you'll have to separate the settings you want out of the file and create a new _settings.sass or something along those lines. -Lorin On Apr 8, 2011, at 12:02 PM, Chris Roth wrote: > Is it possible to import another SaSS file to access its variables and > mixins without generating its CSS? > > I need to grab the variables (I'm using them as settings) from some > other SaSS files, but I don't want them to be compiled because I want > the browser to load them individually so they can be cached, as they > apply to every page on my site. > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to haml@googlegroups.com. > To unsubscribe from this group, send email to > haml+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to haml@googlegroups.com. To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
