The haml and sass executables in trunk now accept a -c flag, like the ruby executable, that causes them to only check syntax and not output anything (or evaluate any code, in the case of Haml).
Rich Morin wrote: > When I run the following code: > > ... > - if flash[:notice] > .notice= flash[:notice] > ... > > through haml(1), I get this nastygram: > > NameError on line 26: undefined local variable or method `flash' for > #<Object:0x6f9844> > Use --trace to see traceback > > I suspect that this simply reflects the fact that that I'm not running > Haml under Rails, so > no "flash" array has been defined. This is understandable, but a bit > annoying, given that > I'm just using haml(1) to check my HAML syntax, etc. > > I'd like to see one or more options that would allow me to control > haml(1) processing. I > don't know much about the innards of Haml, so I won't try to be > specific, but limiting the > processing to a syntax check might be one reasonable option. > > -r > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
