doesnt seem consistent, i think scss expects the value to be quoted and sass expects it not eg
.scss @include 'foo' .sass @include foo On Apr 1, 2010, at 1:46 PM, Chris Eppstein wrote: > @include and @mixin will work in .sass files too for consistency. > > chris > > On Thu, Apr 1, 2010 at 10:39 AM, Charles Roper <reac...@charlesroper.co.uk> > wrote: > Hey Yehuda, > > Those are for SCSS, not Sass*, aren't they? I'm thinking SCSS probably needs > it's own syntax. Or have I misunderstood what you're asking for? > > *"Sass" being the whitespace-sensitive indented style without curly braces > that uses + and = for include and mixin definitions. > > Nathan, is there a preferred term we should settle on using for the "classic > whitespace-sensitive indented style"? The docs suggest it's called "Sass", > but that could be confusing seeing as SCSS is still Sass, kind of. Perhaps > "Sass Classic"? Not sure, what do you reckon? Maybe the term SCSS just needs > a little time to bed in? > > Charles > > > On 01/04/2010 16:54, Yehuda Katz wrote: > Could you also add @mixin and @include syntax (for = and +)? > > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 > > > On Thu, Apr 1, 2010 at 2:24 AM, Charles Roper > <reac...@charlesroper.co.uk <mailto:reac...@charlesroper.co.uk>> wrote: > > I've just pushed a minor update to my fork of the Sass tmbundle: > > > http://github.com/charlesr/ruby-sass-tmbundle/commit/ed9028749f5c8ffb6616c370d2902d00a3932e95 > > It just fixes the variables in whitespace mode (not SCSS, which I've > not looked at). I'm not able to test on TextMate so could someone do > the honours and see how it looks? This is what it looks like in e: > > http://i.imgur.com/pzfDs.png > > > Charles > > -- > 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 > <mailto:haml@googlegroups.com>. > > To unsubscribe from this group, send email to > haml+unsubscr...@googlegroups.com > <mailto:haml%2bunsubscr...@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 h...@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 h...@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 h...@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. -- jonathan linowes parkerhill technology group llc jonat...@parkerhill.com office: 603-838-2884 killer app: http://reviewramp.com tech blog: http://vaporbase.com personal blog: http://jon.linow.es twitter: @linojon -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to h...@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.
