hudochenkov / syntax-highlighting-for-postcss Goto Github PK

Somehow, on my ".pcss" files that are edited with PostCSS, I do not get any auto complete.

I created a `../User/PostCSS.sublime-settings' file with:

{
  "auto_complete": true
}

but still no luck.

Love this plugin, but I really miss autocompletion, even the most basic ones.

@hudochenkov hi, thanks for syntax highlighter. It becomes extremely useful to add PostCSS support to GitHub.

But they need a LICENSE file in the project root.

They need some license from this list. I recommend MIT.

This one is very well done and complete.

https://github.com/y0ssar1an/CSS3

Using attr, format, or url with string concatenation ruins proceeding syntax highlighting. I believe a fix would be as simple as changing:

<string>(?&lt;=url\(|format\(|attr\().+(?=\))</string>

to

<string>(?&lt;=url\(|format\(|attr\().+?(?=\))</string>

in Syntaxes/PostCSS.tmLanguage

Sample of issue:

Sample of fix:

Fork badge is bad, because your repo doesn’t showed as separated project.

You can send a email to GitHub team and they will remove fork status.

CSS next feature for reference

You are going to add SugarSS?

Hello,

I need to be able to set all .css files to use the PostCSS syntax, however, it is not listed as an option.

Please can you advise or fix?

Thank you!

Since this highlighting is fork of SCSS highlighting I didn't change syntax scope from source.scss. I did this for other Sublime Text plugins compatibility. They are relies on scope and know nothing about source.postcss scope. This bring up issue when comments settings for PostCSS and comments settings for SCSS is conflicted and Sublime Text uses only PostCSS settings (at least in my setup). This is not breaks SCSS, because it's standard CSS comments (/* */), but it's not user expecting.

I'm waiting for adding PostCSS compatibility to following plugins in order to fix this issue:

• CSSComb 4.0 release Doesn't matter because for sorting reason may be replaced by sublime-postcss-sorting which have better sorting abilities.
• My PR to Emmet sergeche/emmet-sublime#587

Auto-complete (tab completion) is not functional.

Midas is a awesome highlighter for PostCSS
https://github.com/ben-eb/midas

There seems to be a slight bug when a variable name follows a space and an opening parenthesis.

This doesn't highlight correctly:

max-width: calc($desktopImageSize * ($desktopColumns - 1));

This does:

max-width: calc($desktopImageSize *($desktopColumns - 1));

Hello,

I've got small problem with Emmet autocompletion.

For example:

/* Colors */

$pelorous : #3fbcc0;
$flamingo : #f54b38;

Now, when I'm trying to c -> tab to get color property, it autocompletes "Colors" from my comment. It does not happen on basic CSS syntax highlighting.

Thanks in advance and thanks for all good work.

This is the finest syntax highlighter I’ve used with Sublime Text. Could it parse valid CSS variables? Would it be in scope to parse Sassy variables?

The subtle highlighting of var and --hello make a world of readability difference.