Stylus: Stylus-lang preprocessor should apply block comment on Ctrl-Shift-/

[dnknn]

UserCSS editor (i.e. single-editor, not classic editor ) , @preprocessor stylus mode,
cannot use CSS comment, i.e. /* */

Hotkey  |  Specific issues
--- |---
Ctrl+Shift+/ | invalid, totally unusable
Ctrl+/ | valid, but typing //

[tophf]

Usercss can use Ctrl+Shift+/ and /* */.

For Ctrl+/ it depends on the preprocessor: in less and stylus both types of comments are valid. You can configure Stylelint to hide the warning, there's a gear icon next to the linter selector. Refer to Stylelint documentation for more info.

The rule name is no-invalid-double-slash-comments (you can see it when hovering the error message in the report on the left).

[tophf]

The errors about // will be hidden now: 6d7bd650. Turns out they were shown because we don't apply preprocessor before linting (otherwise line numbers will be nonsensical).

[dnknn]

@tophf thank you! Completely beyond the scope of my knowledge :)
I always thought // is a dedicated comment syntax of javascript code, In addition, different @ preprocessor are distinguished here.
I don't know use other preprocessors, I personally only know @preprocessor stylus , I think Stylus-lang is more concise and straightforward than other preprocessors, so I chose it as the research object at the time.
However, in the @preprocessor stylus mode, can not use Ctrl+Shift+/ , if can use Ctrl+Shift+/ to type /* */ , it is better!

[tophf]

However, in the @preprocessor stylus mode, can not use Ctrl+Shift+/

Aha. Sounds like a bug, gonna investigate.

[tophf]

This is indeed a bug in stylus-lang addon for CodeMirror, I've submitted a patch in their repository so the fix will be shipped soonish, I guess.

[dnknn]

Thank you very much!

[tophf]

@dnknn, keep spamming me with useless comments everywhere and I'll get annoyed to the point of blocking you from participating on this repo. Simply use the reaction buttons.

[dnknn]

Sorry...Sorry! I don't know. Ok, I see, not next time! sorry.