Takes the LESS syntax as a basis for a complete rewrite of the SCSS syntax. Structurally the languages are very similar, with similar challenges.

The LESS syntax was rewritten recently over several months of testing and fine-tuning. It bases as much as possible on the default CSS package which has seen a lot of improvement since being open-sourced. Like the new default syntaxes LESS adheres to the new scope naming guidelines, and has similar nuances like scoping the $ and @ in variables and at-rules, or the quotes around string separately.

This also enables the completions from the default CSS package, fixing issues like #72 #93 #49.

This PR also fixes #85 and probably some other things too.

Let me know what you think. I also want to update the tests using Sublime's new test engine, and finally also upgrade the sass syntax.

I am missing this feature in sass, it works fine with less bundle https://github.com/danro/LESS-sublime but not in sass, i tried to modify Symbol List - Selectors.tmPreferences file, but no avail. May be i am missing something?

Normally when i click on an opening or closing bracket, the other end is underlined. This works in the SASS version but not the SCSS style (on a .scss file).

For some reason this syntax mode crashes Sublime every time. I've used for some a while but suddenly it started causing crashes. I had to remove every plugin and install one by one to isolate the issue.

Since then, and after I reinstalled Sublime, i've managed to cause the crashes again by installing this again.

Is there anything I can do to help identify what may be the cause?

Whatever you've changed in the last day has caused Sublime to crash when trying to open SCSS files. I've had to remove this package to actual continue with my work. When opening an SCSS file I get the blue loading bar (the same one you get when opening a large file), it then just hangs and crashes the entire program.

I'm using Mac OS X version 10.9.2.

If there's any information I can provide to help, let me know how to get it and I'll try and provide it.

Hi, the sass-3.3 branch has been working for a while now. I've changed many match rules and I am not sure they will work perfectly. Please help me to test it and if you see any problems or have any suggestions (No matter how small it is), feel free to give me a shot. Thanks

Please remove this package through Package Control firstly, and then clone or download the sass-3.3 branch into the package folder of Sublime Text.

I'm having a problem where its not working for .sass files. I need to go into the command palette and set the syntax manually. It works fine for scss.

I'm using build 3053.

I'm using Emmet ex Zen Coding & the code completion was working with SCSS & Sass files without a problem when I was a different Sass package. after I installed this package Code completion is not working in SCSS as it used to be.

Hey. Just tried this plugin in ST3, but when I open a file with extension .scss, it comes up with a red background on all the curly braces. In the syntax menu it's mistakenly using "Sass" instead of the "SCSS" syntax. (The former uses the extension .sass.)

For some reason, you can get into a bit of trouble being able to define mixins using the .sass shorthand way (=) following a comment. Take for instance the following below.

// ## Why @at-root? 

// Because it's not ambigious what's going on with the ampersand now being able to be used outside of the context of things from before 

=increased-specificity($selector: &) //The mixin is grayed out. 
  // Logic I had here. 

Have noticed this a variety of times (with the .sass file rendering fine) and decided to finally report the issue.

The latest version has completely broken the symbol browser in ST3 where the window is filled with everything

WITHOUT:

Installed:

As you can see with it being installed, it's completely filled the symbol browser with everything single variable or mention of a variable in the current file

I have the Sass package installed in ST3 v3.1.1 Build 3176. I've been having this issue when I save a .scss file in ST3 any single line comments using // automatically are changed to multi-line comments using /* */. It appears to be a bug but could also be a conflict with another formatting package I have installed.

Just to be clear, this means I am unable to have invisible comments in my .scss files, as all the comments get processed to my .css file.

I did extensive Google Searches and found nothing so I'm checking here to see if anybody has any solutions.

Cheers.

When I hit ⌘R in a CSS file, I see each selector on its own line, no matter how many tokens it contains. But with this package in an SCSS file, for example, body > header becomes two symbol browser entries: body and header.

Screenshot below. Is this normal? I've disabled every package I can imagine interfering with this one.

• Sublime Text 3176
• Sass package v1.2.4
• MacOS 10.13.5

It looks like I can't have the cake and eat it, too.

The problem: CSS3 extension requires the "file type" to be set to CSS3 to take effect. The same goes for the SASS extension to enable SASS relevant support.

So it appears that both extensions are mutually exclusive, as I can't seem to configure any to also be active when the other file type is being loaded.

Any ideas on how to enable both CSS3 autocompletion + SASS support for a *.scss file?

Thanks! Oliver

I've been trying forever to get autocompletions to work for SCSS but it never works. Do you know how I can do that? or is that package purely for highlighting?

For example if I start typing just for justify-content:, nothing ever show's up. It only knows basic CSS2 stuff.

As the following screenshot shows, Sass map's key-value pairs are displayed in the same color, unlike property name- value pairs in CSS declarations. I am not sure how you guys feel, but personally I prefer to have a clearer distinction between them.