The first bug appears to be related to the first-line in the file, when I use /* on the second line, surprisingly it works.
On Tue, Apr 1, 2008 at 5:23 PM, Evgeny <[EMAIL PROTECTED]> wrote: > Another comments bug, > > sass: > :font-size 62.5% // Resets 1em to 10px > > css: > font-size: 62.5% // Resets 1em to 10px; > > Notice that the ; is at eol instead of before the comment > > Is this even supported? > > And what about sass-only comments, that wont get rendered > into the css file? > > > PS: I am using Haml 1.8.2 gem and the "sass" command for these results. > > > On Tue, Apr 1, 2008 at 4:54 PM, Evgeny <[EMAIL PROTECTED]> wrote: > > > I stumbled on a "bug" today when using the "sass" command line utility > > to convert > > a sass file with comments to css. > > > > The sass file just had several lines commented with /* */ at the top. > > > > After running "sass input.sass output.css" the output file two problems. > > 1. the comments were gone altogether, and replaced with an empty string > > "/* */" > > 2. there were many empty lines where the comments should have been > > > > What I was expecting is the comments to appear, and in case they didn't > > appear > > then at least the output.css not look like a badly written php html with > > empty lines > > all over the place. > > > > The comments have to appear there because it's special metadata for > > wordpress, > > wordpress actually reads from there the theme name, description, etc .. > > for that theme. > > > > > > - evgeny > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
