But in that case the tool only reacts if I modify the style.scss... I could do both: Use the style.scss with @import and let sass scan for all files. But it will produce errors if I use variables in one file which were defined in an other file. I'll also get files I don't want to have.
What I mean is: sass should check the imported files for modifications. Or the usage like: sass --watch scss:css/style.css.. So it checks for all files, but merges them into one single css. On 22 Okt., 21:43, Nathan Weizenbaum <[email protected]> wrote: > The idea is that you have a single style.scss that @imports both app.scss > and typo.scss. > > > > On Fri, Oct 22, 2010 at 12:36 PM, twols <[email protected]> wrote: > > Yes, but if I have app.scss, typo.scss e.g. the tool creates app.css, > > typo.css.. But I want only one merged file (style.css). Variables are > > also not shared if I use it the way you suggest. > > > On 22 Okt., 21:33, Nathan Weizenbaum <[email protected]> wrote: > > > If you use sass --watch path/to/sass/directory:path/to/css/directory, > > > whenever any file in the Sass directory changes, it will update any CSS > > > files that would be affected by that change. > > > > On Fri, Oct 22, 2010 at 12:25 PM, twols <[email protected]> > > wrote: > > > > I've started using SASS today (it rocks btw), not only for my rails > > > > app, also for php-based sites. So I'm using the sass command line > > > > tool, really easy, but one thing is annoying: I can't merge multiple > > > > scss files into one. I can let the sass-tool scan for changes in all > > > > files, but it also creates the css files for every scss-file. But I > > > > want to merge them all into one single style.css. And I want to share > > > > the variables between all stylesheets. I could use a style.scss with > > > > @import .. but in that case the sass tool don't see the changes in > > > > included files.. > > > > > Is it any possibility to merge the files? Or let the sass cli reacts > > > > on every change in the folder? > > > > > -- > > > > 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]<haml%[email protected]>< > > haml%[email protected]<haml%[email protected]> > > >. > > > > 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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected] <haml%[email protected]>. > > 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 [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.
