By "nested" I mean that the text should be intended beneath the /*, like so:
/* This is a comment Comment comment comment Evgeny wrote: > Should comments even BE nested at all? (The /* comments i mean) > > On Fri, Apr 4, 2008 at 9:59 PM, Nathan Weizenbaum <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Okay, I've figured out what's going on. When you write what's in > option #2, Sass first sees one CSS comment. This comment has no > content and nothing nested beneath it, so Sass thinks it's empty. > The next four lines Sass interprets as selectors with no content - > and thus renders empty lines for them. > > > On Wed, Apr 2, 2008 at 7:45 AM, Nathan Weizenbaum > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > Alright, I'll look into it. > > For the record, closing comments in Sass is wrong and will > produce the wrong output. This just isn't the right wrong > output for it to produce. > > Evgeny wrote: > > Check the option#2 sass and css > > http://pastie.org/174074 > > > On Tue, Apr 1, 2008 at 7:10 PM, Nathan Weizenbaum > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > I'd like a simple file that demonstrates the first issue. > > Sass doesn't support inline comments. > > - Nathan > > Evgeny wrote: > > 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] <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > > <mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] > <mailto:[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] > <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > > <mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] > <mailto:[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 -~----------~----~----~----~------~----~------~--~---
