<![CDATA[CSS comments should be in GREEN]]>Why are CSS comments in BLACK when all other comments are GREEN?
comments.PNG

]]>https://community.notepad-plus-plus.org/topic/24940/css-comments-should-be-in-greenRSS for NodeSun, 16 Aug 2026 01:16:16 GMTTue, 19 Sep 2023 15:37:21 GMT60<![CDATA[Reply to CSS comments should be in GREEN on Wed, 04 Oct 2023 01:54:44 GMT]]>@Gulshan-Negi-0 said in CSS comments should be in GREEN:

Well, in my opinion and knowledge, the comment color of CSS is customizable, which means you can change the color of CSS comments.

This topic is about inline CSS between <style>...</style> tags in HTML documents. You are talking about standalone style sheets with the *.css extension.

To demonstrate that you cannot set the style of inline CSS in HTML files, you can try the following:

  1. Save this markup as index.html:
<html>
    <style type="text/css">
      /* comment */
    </style>
</html>
  1. Open index.html in any published version of Notepad++
  2. Go to Settings > Style Configurator
  3. Select “Language: CSS”
  4. Select “Style: Comment”
  5. Change the style and save
  6. Observe that nothing happens

html-with-inline-style-npp.8.5.7-002.png

Now select CSS from the language menu at Language > C > CSS, and observe that CSS comments are styled as specified in Style Configurator:

style-sheet-npp.8.5.7-002.png

]]>https://community.notepad-plus-plus.org/post/89666https://community.notepad-plus-plus.org/post/89666Wed, 04 Oct 2023 01:54:44 GMT<![CDATA[Reply to CSS comments should be in GREEN on Tue, 03 Oct 2023 17:03:33 GMT]]>Well, in my opinion and knowledge, the comment color of CSS is customizable, which means you can change the color of CSS comments.
Thanks

]]>https://community.notepad-plus-plus.org/post/89652https://community.notepad-plus-plus.org/post/89652Tue, 03 Oct 2023 17:03:33 GMT<![CDATA[Reply to CSS comments should be in GREEN on Tue, 03 Oct 2023 02:34:08 GMT]]>@deleelee said in CSS comments should be in GREEN:

This is a perfect example of when it would be great to be able to load a default language into the User Defined Language window and make changes.

  1. You can change the appearance of the lexer for a default language, just not in the UDL window.
    • Instead, you go from main menu to Style Configurator-><language name>, choose a style name from the Style list, and customize that style. For more info, see the user manual.
  2. You can’t use the UDL editor to edit default languages because they weren’t made using the UDL system. As rdipardo explained above, the lexer for HTML was written in C/C++ because the UDL system is not powerful enough to capture the intricacies of HTML syntax.
]]>https://community.notepad-plus-plus.org/post/89638https://community.notepad-plus-plus.org/post/89638Tue, 03 Oct 2023 02:34:08 GMT<![CDATA[Reply to CSS comments should be in GREEN on Tue, 03 Oct 2023 01:25:26 GMT]]>This is a perfect example of when it would be great to be able to load a default language into the User Defined Language window and make changes.

]]>https://community.notepad-plus-plus.org/post/89633https://community.notepad-plus-plus.org/post/89633Tue, 03 Oct 2023 01:25:26 GMT<![CDATA[Reply to CSS comments should be in GREEN on Wed, 20 Sep 2023 20:23:53 GMT]]>@mkupper said in CSS comments should be in GREEN:

If I am viewing an .htm file that contains a <script>…</script> is the lexer/formatter/highlighter/colorizer code at all related to the lexer/formatter/highlighter/colorizer code that would process the same chunk of JavaScript in a .js file? Or are they 100% unrelated code paths and updated/maintained independently?

HTML is styled by this lexer module, which defines styles for all generic SGML markup (XML included) as well as (very basic) JavaScript, ASP and JSP scripts, and (Python) Mako templates, but not <style> elements.

There is also a complete module for independent style sheets with the *.css or *.scss extension.

It’s well documented that there’s no styling of embedded CSS in HTML documents. You can read through this (partial) list of open bug reports, the oldest dating from 2005:

There really is no simple way to programmatically switch between completely different lexer modules in the same editing window. Scintilla is basically a synchronous, single-threaded service running inside the application (despite the addition last year of optional parallelization for line layout).

What VS Code and other Textmate-based editors are doing is basically regex matching. The EnhanceAnyLexer plugin for N++ can provide something like that by setting custom styles for portions of the document that match a user-defined regex.

]]>https://community.notepad-plus-plus.org/post/89390https://community.notepad-plus-plus.org/post/89390Wed, 20 Sep 2023 20:23:53 GMT<![CDATA[Reply to CSS comments should be in GREEN on Wed, 20 Sep 2023 16:39:15 GMT]]>@Mark-Olson I don’t know much about the lexer stuff and Lexilla but have some questions related to your comment about “Lexilla has to reinvent the wheel whenever it wants to have different languages in the same document.”

If I am viewing an .htm file that contains a <script>…</script> is the lexer/formatter/highlighter/colorizer code at all related to the lexer/formatter/highlighter/colorizer code that would process the same chunk of JavaScript in a .js file? Or are they 100% unrelated code paths and updated/maintained independently?

If I copy/paste the CSS from within the <style>…</style> section of an .htm file into a .css file I see that the css is colored nicely, including green comments. I assume that means people have written and maintain a css lexer/formatter/highlighter/colorizer that works with Notepad++.

]]>https://community.notepad-plus-plus.org/post/89376https://community.notepad-plus-plus.org/post/89376Wed, 20 Sep 2023 16:39:15 GMT<![CDATA[Reply to CSS comments should be in GREEN on Tue, 19 Sep 2023 21:11:37 GMT]]>@Sanford-Arbogast
TLDR: This seems like a problem that will probably never be fixed.

It would seem that the reason for this is that the HTML lexer for Notepad++ does not have a built-in sub-lexer for CSS, but it does have one for JavaScript.

That is, when Notepad++ is colorizing an HTML document, if it detects a <script> tag, it goes into a new state where it colorizes based on JavaScript syntax rather than HTML syntax. But because it has no sub-lexer for CSS, when it hits a <style> tag, it treats the contents as plain old text.

Unfortunately the Lexilla library that Notepad++ uses for syntax coloring is rather low-powered compared to say, the TextMate-based lexer for VSCode, so whereas VSCode can divide a document up into sections that are each colored according to completely different lexers, Lexilla has to reinvent the wheel whenever it wants to have different languages in the same document. This means that a seemingly simple idea like “use CSS rules for syntax coloring inside of <style> tags” has a lot of programming overhead for Notepad++ that makes this kind of problem unusually irritating.

That’s not to say you couldn’t hack together your own workaround. But unfortunately nobody is likely to ride in to save the day here.

]]>https://community.notepad-plus-plus.org/post/89360https://community.notepad-plus-plus.org/post/89360Tue, 19 Sep 2023 21:11:37 GMT