You can import the config stylesheet into your generic-elements stylesheet or since you're probably only using these files for importing and not as stand-alone css, you can rename the files to start with an underscore and no css file will be generated for them. (note: you don't have to change the import statements for this rename.) I'd also encourage you to add .sass to your imports so that there are compilation errors if the files are not found.
Chris On Fri, Jan 23, 2009 at 7:05 AM, andysky <[email protected]> wrote: > > There's a problem I'm having -- I've got a main sass file, called > "application.sass" where I have two imports, like this: > ----- > @import config > @import generic-elements > ----- > > in the "config.sass" I initialize a couple of variables, such as: > ----- > !links_color = blue > ----- > > then, in the "generic-elements.sass", I call this variable: > ----- > a > > &:link > :color = !links_color > ----- > > everything works fine in the generated (full) css file, > "application.css", but all the "component-only" files are also > converted to .css and, for example, the "generic-elements.css" has an > error message: > ----- > /* > Sass::SyntaxError: Undefined constant: "!links_color". > [...] > ----- > > SASS is trying to convert these "component-only" .sass files as if > they were independent -- how can I prevent this from happening? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
