I've just pushed a fix for CK's issue. On Thu, Jul 22, 2010 at 11:46 PM, CK Ng <[email protected]> wrote:
> Well, perhaps the feature request can be ignored. Just found out it > will work under scss. > > On Jul 23, 12:57 pm, CK Ng <[email protected]> wrote: > > There is an additionalbugon comment block, where an additional '*/' > > is generated at the end. Tested inhttp://sass-lang.com/try.html > > > > Sass: > > /** > > * @file a.sass > > */ > > > > Generated CSS: > > /* > > * @file a.sass > > */ */ > > > > As for the '*/' support on sass, my opinion is that for comment, it > > should be copy exact without any conversion. From the above example > > also, we needed the '/**' for documentation purposes, preferably in > > CSS, however sass has removed the critical '/**' to '/*'. I suppose we > > will have problem if we want to document the sass, without the ending > > '*/' > > > > Hope you will consider to add in support for > > - comment copy exact, or > > - beginning '/**' and ending '*/' > > > > CK > > > > On Jun 1, 12:10 pm, Nathan Weizenbaum <[email protected]> wrote: > > > > > I've just pushed a fix for the extra-*bug. > > > > > On Mon, May 31, 2010 at 9:01 PM, Nathan Weizenbaum <[email protected]> > wrote: > > > > If your editors' syntax highlighting requires a */, that's abugin the > > > > highlighting, and I'm not willing to change sass-convert to > accommodate such > > > > abug. The standard Sass style is to omit the */, so that's what > > > > sass-convert generates. > > > > > > It is abugthat the generated Sass adds an extra *. I'll look into it. > > > > > > On Mon, May 31, 2010 at 8:11 PM, Matt Martini < > [email protected]>wrote: > > > > > >> Chris, > > > > > >> $ sass comment_test.sass > > > >> /*-------------------------------------------------- > > > >> * GENERAL > > > >> * *-------------------------------------------------- */ > > > > > >> Ok, you are correct, even though css->sass->css does not > > > >> give back what I started from. > > > > > >> $ cat comment_test.css > > > >> /*-------------------------------------------------- > > > >> GENERAL > > > >> -------------------------------------------------- */ > > > > > >> The bigger problem I have is that my editor (BBEdit) does not > understand > > > >> that the comment is closed (it is looking for the closing */ ) > > > >> so the whole rest of the document is a comment. TextMate also > doesn't > > > >> realize that the comment is done and makes the rest of the document > > > >> a comment too. Vim actually does the correct thing. > > > > > >> Is there a way for the */ to be included? > > > > > >> Matt > > > > > >> On May 31, 2010, at 10:49 PM, Chris Eppstein wrote: > > > > > >> Sass comments are closed by an outdent, they don't need to be closed > by > > > >> */, but they may if you so desire. > > > > > >> You can verify this by viewing the generated css of your sass file. > > > > > >> Chris > > > > > >> On Mon, May 31, 2010 at 7:45 PM, Matt <[email protected]> > wrote: > > > > > >>> Nathan, > > > > > >>> $ cat comment_test.sass > > > >>> /*-------------------------------------------------- > > > >>> * GENERAL > > > >>> *-------------------------------------------------- > > > > > >>> The comment is opened on the first line and never closed. * > GENERAL > > > >>> and *------ > > > >>> are not valid comments. > > > > > >>> Matt > > > > > >>> On May 31, 7:01 pm, Nathan Weizenbaum <[email protected]> wrote: > > > >>> > I don't see the problem here. All the Sass output seems perfectly > valid > > > >>> to > > > >>> > me. > > > > > >>> -- > > > >>> 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]<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.
