nathos / sass-textmate-bundle Goto Github PK

I'm writing in .scss and out of nowhere all my highlighting went to plain text. Whacky. Any body seen that happen? I removed, reinstalled, and updated etc. No deal so far.

Might be the same cause of #77 but single quotes are not highlighted the same as double quotes, though both are valid:

@import "styles-a";
@import 'styles-b';

Hello and thank you for this bundle!
I installed and followed the instructions:

You may find that when you open files with the .sass extension, Sublime Text 2 initially interprets the syntax as HAML. To permanently fix this, open Packages/Rails/Ruby Haml.tmLanguage and delete the line sass.

but I can't find the dir specified.
under ~/Library/Application Support/Sublime Text 3/Packages/
I only have
BeautifyRuby/
PyV8/
User/

I am on Sublime 3
Mavericks

Any help very much appreciated
Thanks again!

When writing SASS, the <header> and <footer> are correctly highlighted as HTML elements (red), however the <main> HTML5 element remains unrecognised (white). Can you add this to the elements list? Thanks!

The description of this repo says it only work with Sublime Text 2, but the package info indicates it works with ST3 also.

Stardard Sublime CSS highlighter adds colons and semicolons as you type in rules, which is VERY convenient. Please add this feature.

Ex:
position: relative;

as you type 'pos' and them hit Enter to complete the word, it should add a colon at the end like 'position:' , same with 'relative;' it should add a semicolon at the end;

ps: Thank you for a great bundle!

There was a relatively recent addition of the <main> element to HTML. This doesn't seem to be detected and highlighted like other specified tags (this also occurs with Sublime Text's native CSS highlighting so possibly related).

Any way to have the bundle respect the CSS insertions of semicolons for SCSS files? Not sure where in the code that is - haven't had a chance to dig in yet. Figured I'd ask.

I've noticed some inconsistencies in the SASS highlighter:

1. Integer values are highlighted but not float values
2. Variables are not highlighted differently
3. Would be nice if values after colon could be highlighted differently as well

Thanks for considering :)

In Sublime Text, I noticed that when I do something like background: url("image.png"); the quoted string is not highlighted. Looks like the definition for url() (lines 107-114) are overriding that of quotes.

Does url() need special treatment? For me at least it doesn't show up as highlighted at all anyway. You could remove that entire section and just have url as a keyword in the support.constant.property-value.sass section.

The highlighting for table-layout css property seems to be undefined.

Version 3.3 of SASS improves the '&' selector in a way that the syntax highlighting currently doesn't cope with. I've spent some time trying to cobble something together, but I'm not sure if there's a nice way of doing this, as the correct highlighting will actually depend upon the parent selector.

I get no @import directives highlight in .scss files:

Arch Linux, ST3 build 3095

I'm sending the names of placeholder selectors to a mixin that applies @extend and the % symbol. A single color would suffice.

Hi there,

Running Sublime Text 2 version 2.0.1 on OS X 10.8.3

I could swear that completion in Scss files used to work similar to that of CSS files, where hitting tab or enter on the property would complete it, then add the requisite colon ( : ) and wait for the value, then add in the semicolon ( ; )

I could be mistaken of course, but I am wondering first does that make sense, and second is there way to duplicate that behavior?

I can see inside of the default CSS package, in css_completions.py around line 143 (for me) is where this action appears to be defined, however I am not sure if there is a way to duplicate that in another package?

Would appreciate any insight, thank you!

Went to install this package via Package Control Installer on ST2 and it is no longer listed?

When searching 'Sass' here's what's listed:

• SASS Build
• SASS Snippets
• Sass-Director
• SassBeautify
• SassBuilder

Will this package eventually be able to compile SCSS files into CSS? Right now I use two other packages just to get the job done. It'd be nice if this could be done with just this one package, that's all it seems to be missing.

Hi, I was having an issue with sass-textmate-bundle while doing Michael Hartl's Rails Tutorial. I installed this via Package Control and got an error of Sass syntax not loading.

For those who are also experiencing the issue, just rename the Sass folder to SASS and the two files under the Syntaxes folder with the all caps SASS. The syntax for scss are now working.

I used the "mv" command to do so. Is it the right way of doing it? Viewing the Packages folder, it created another folder with the new folder and file names.

now, $vars are in white and difficult to read.

Is it just me, or are the colors weird in ST2? Recently all the selectors turned green in the monokai theme.

Sass doesn't show up in ST3 package control for me. SASS Build, snippets, director, and beautify show up, but not this plugin.

Something weird is going on when writing code in different "levels".

For example, in a "level 1" notation like below, no colon is entered when auto-completing a property, and some properties don't show up in the auto-complete list (like font-style). If I however add a second level element inside that one, all of the above suddenly works.
Except adding a semicolon at the end.

Example:

.level-1 {
    width: 100%; // No automatic colon when auto-completing for "width"
    font-style: normal; // "font-style" doesn't show up in the auto-complete list

    .level-2 {
        width: 100%; // Colon is automatically added when auto-completing "width"
        font-style: normal; // Auto-completion for "font-style" works
    }
}

Also see here: #37

Hi,

after the last update Sublime Text says, that it can not format SASS/SCSS files. I removed the package, reinstalled and after one day I get the same error.

Could this be a bug?

Why aren't the units highlighted?

CSS

SASS

Merge this repo into sublimehq/Packages.

There is no @media parameters specific coloration.

Eg. @media screen:

When using the Sublime theme, "Pastels on Dark", the scss color scheme is practically non-existant in comparison to the default color scheme. Can we get more colorful highlighting, please? Thanks :)

EDIT: Woops, nevermind. I meant to go to the SCSS package.

Hey, possibly something simple, but I couldn't find it within your syntax file and something that I noticed is that syntax highlighting seems to be a little off. For example, the image attached shows proper highlighting for -webkit-box-shadow but now -moz-box-shadow.

BTW, thanks for the plugin. Use if purely for the syntax highlighting (as of right now) and it's been pretty great! :D

At the moment when I use the sublime shortcut for comment block alt+command+/ within a .scss file I get a inline comment rather than a block comment.

// this is a comment
rather than
/* this is a comment */

Is their anyway that you can correct that within the plugin

I am not getting the auto-complete box appear with fuzzy search while typing css properties. Is this supposed to appear?

Would it be possible to add support for the goto-symbol shortcut? On a regular css file this displays all the properties in that css file.

IMHO it would be nice to improve the structure of this repo or split it into two differents, one for Textmate and another for Sublime. The problem here is that master branch is around 50 commits ahead of sublime and due to this fact syntax and completion files are totally different between them.

Another problems to solve:

• Reflect in README.md that there's a specific branch for Sublime
• Use git tags for Package Control versions
• Add tests
• Add messages for Package Control

I'm ready to collaborate as a mantainer or contributor to help to implement this features.

Hello,

I realized I had some changes to the text highlight Sass. Now he shows image links as a comment.

Would not it be better if the text highlight the style to be the default path, and link or not?

[]'s

For example: background-image: url("my_image#{($h * $w)/2}.png");
The closing parens end the url() highlighting, when they should either be ignored or end the order highlighting (which is not currently supported).

Currently I'm getting shouted at (in bright pink no-less ;)).

Hi there,

I have the SASS plugin installed for ST3 and it appears to work but for example if I type bdrz it autocompletes to Border-Radius but if I type border I get no autocomplete for border-radius

In the css file it works.

Is this configurable in any way so that it works by enter the full word ie.. Border ??

I have the syntax (lower right) set to sass

Thanks

Hey folks,

today I've started ST2 and noticed the lack of Sass syntax highlighting. I tried to choose it from the menu in the right bottom corner but Sass isn't listed there. I've reinstalled the plugin twice but it is still not working. No reports in the console log.

I'm trying to follow your installation instructions and I'm having problems. First of all when I enter the osascript command into terminal I get back a "syntax error: A identifier can’t go after this identifier. (-2740)" message.

Also, when I go to the command pallette Install Packages is not listed in Sublime text v3 (build 3065).

http://unakravets.tumblr.com/post/78744593423/sass-snippets-the-almighty-ampersand

"&__header{", "&__text{" and "&--link{" are not colored.

.speech-bubble{
  color: purple;
   &__header{
    color: orange;
  }
   &__text{
    color: black;
     &--link{
      color: green;
    }
  }
}

The current version of Sass.tmLanguage has two snippets of non-XML code in it on lines 158, 159 and 204:

<<<<<<< HEAD
=======

>>>>>>> 28ecb93... added highlighting for -moz-box-shadow. Fixes #13

Not sure if something went wrong with merging or committing?

Hi guys.
I have SublimeText 2.
When I change to Sass file, I lost the CSS intellisense. But, if I come back to CSS file, I get again the intellisense but losing your colors.

Is there a solution for that?

.scss is highlighting but not .sass? any ideas?

I solved the lack of compatibility between this nice package and Emmet:
With those two things, you will be able to press the key tab to expand an abbreviation with Emmet, and a ";" will be put at the end of the abbreviation line (like with a css file).

2 things:

• For Sass-textmate-bundle : you have to delete the folder "Snippet" in order to let Emmet do his job (press tab to expand an abbreviation...).
  You have to delete it directly in the archive folder of ST -- otherwise it will be rebuilt next run time. So go to "Installed Packages/Sass.sublime-package" -> rename it "Sass.zip" -> edit it with winrar -> within delete the folder "Snippet" -> then rename it "Sass.sublime-package" -- works for ST3, Sass-textmate-bundle downloaded with package manager.
• Finally, what you had to find ;] : in Emmet folder, you have to edit the file "Emmet.sublime-settings" and add "sass.propertyEnd": ";" (with all the quotation marks) here :

"preferences": {
        // "css.valueSeparator": ": ",
        // "css.propertyEnd": ";"
        "sass.propertyEnd": ";"
},

Voilà, voilà!

Hope this can help someone.

#38, #37, #28, #12, #10

When adding a multi-line comment, only the first line is treated as a comment. All subsequent lines are treated a regular text.

While working with the content attribute, I found out that the following will break the syntax highlighting

content: "'"; // this works
content: '"'; // this doesn't

I am using scss files and I am seeing autocompletion for variables defined in the same file; But not for variables defined in other files in the project imported. Is it not possible to get autocomplete for variables defined in separate files?

Using Compass Sprites, the following becomes a problem:

@import sprite-files/*.png
// Every line after this is shaded as commented out,
// including .png above.

Not entirely sure how this could, nor whether it should, be fixed. Related to #7.

When opening a .scss file it does not auto load the syntax. I have to manually change it in the console or the GUI in the bottom right..

Is there a watch or auto-load function?

I'm new to github and just now picking up SASS and Sublime Text 2, so hopefully I'm not missing something obvious. I've installed the package and selected the Sass extension. Highlighting is working just fine, but I can't seem to get the included completions to show up.

For example, I'll type "@include tran" and I'll only see completion options for "transparentize" and "transition", but I'm actually looking for "transition-property", "transition-duration", and "transition-timing-function". Even typing up to "@include transition-" these options still don't show.

Is there something I'm missing? Do I have to activate the sass completion list somehow? Are there known conflicts with other packages that could be preventing these completions from showing? Any help would be appreciated.

Btw, I understand there's already an open thread for "Auto complete doesn't appear" but that's over 8 months old.

I was running my latest dotfiles repo and it appears that Sass has been removed from Package Control in Sublime Text 3.