Syntax-highlighting-for-Sass
Syntax-highlighting-for-Sass copied to clipboard
P233
.scss autocompletion gone in sublime text 3
After the last update the autocompletion in the .scss files dosn't work anymore but in the .sass files.
System: Windows 10, Sublime Text 3
Just re-install the plugin. It works for me (totally remove package and install it from scratch)
Didn't work. After removing Emmet too the autocompletion works as expacted, but that's not an option.
For me both scss and sass not work today.
System: Windows 10, Sublime Text 3
Ok sorry, just read the New Features section Removed built-in completions
Emmet Css Snippets appears to have absolutely the same autocompletions and: "Works with default CSS package, LESS, and Syntax Highlighting for Sass"
Right, I also missed the "Feature" description. Hm I will give the Emmet CSS Snippets a chance.
This pack work perfect for me: Emmet Css Snippets - for props like color, height etc. SASS Snippets - for functions such as rgb()... Sass - you know
It's really annoying that the built in completion is gone!
For example in SCSS: typing "colo" doesn't complete "color" typing "posi" doesn't complete "position" further "abs" doesn't complete "absolute"
And very annoying: all defined sass/scss variables aren't in the completion
If you switch in scss documents to sass than all work's like before but the curly brackets are highlighted/marked.
Please readd the completion! Parhaps with a flag to activate/deactivate them ...
I've installed emmt and the emmet css snippets but can't achieve a nearly good completion.
The feature
Removed built-in completions
is really a bad idea..
Is there a chance to roll back on this one ? I don't really see the point of removing this important feature (because having it is a feature, removing it isn't) 👎
Hi @P233,
Thanks for the good work on the previous releases... I think we're a lot to have some questions about this 🎉 brand new feature 🎉 that removes the built-in completion of Sublime Text. Here are mine and I hope you have relevant answers to them:
- Why do you need to remove the built-in completion for your package ?
- Why do we need to install 2 more packages because of this feature ?
- Don't you think a package should improve Sublime Text without removing one of it's most used built-in feature ?
- When did you think it was even a good idea ?
I can't imagine the number of hours developers around the world should spent right now trying to figure out why their completion isn't working anymore because of your last release instead of writing code for maybe a next amazing website, application,...
No one here understand the pros of removing a core feature of Sublime Text and the advantage for your package I guess. Personally I really hope it's an April Fool's joke and that you made a mistake reading the date this morning when waking up.
Best regards, Anthony
As a temporary workaround, pull the css_completions.py out of your `Packages\CSS.sublime-package' and modify line 449 (build 3143, may vary on newer builds) to:
css_selector_scope = "source.css - meta.selector.css, source.scss - meta.selector.scss"
Drop the file in your Sublime Packages\User folder, restart sublime and good old CSS completions should be back.
From this thread, it seems that author @P233 is incorporating standard CSS completions back, but the above workaround seems to work for now :-)
Guys, I think the development community would benefit from slightly less grumbling and sarcasm when reporting issues. Let's remember that we are all benefitting from @P233 's work for free.. If issues are important to you, then definitely report them, but maybe with a bit of grace for things you don't understand or possible errors :-)
Hi,
In terms of the "Removed built-in completions", I was comparing with the previous version of this package which happened before this package takes over the package name of "Sass".
In the ST2 version, there was a feature to filter completions based on scopes. But it increased the difficulty and time spent to maintain this package. When ST3 introduced the new syntax definition format, I decided to give it a shot.
Since I don't use ST as my primary editor (except reading code), I want to abandon the completion feature and rely it on the Emmet plugin; then I could focus on the highlighting accuracy and save my free time.
And you could see how I improved accuracy in the new version:
Now I am planning to reorganise scopes which could fix two existing bugs and bring back the completion feature with accuracy popup position. Please bear with me for a while longer.
@P233 Would the adjustments you are talking about bring back auto-completing text that appears in the file (like class names)? I have no problem with using Emmet for props and values, but I use auto-completion as an accessibility feature (I have difficulty typing) to help me type repeated/similar selectors and such.
