@b4n @eht16 OK to merge this PR? I'd like to avoid the situation like with the Raku parser (#3169, also updated on top of 2.0 now) where it rots in open PRs and then, before the release, it's too late to get merged.

I went through the various open PRs and open issues providing/requesting support of certain languages because some seem to be a bit neglected:

There's this PR adding Prolog support.
There's the Raku language support in #3169 which is hopefully in a mergable state.
I created #3647 (Scintilla lexer for JSON) and #3648 (Scintilla lexer for Nim) - for JSON there has already been a pull request in the past and they have also been requested in some open issues and in general I agree that when there's a Scintilla lexer, we should use it.
Yesterday I reviewed #3480 (CIL language support) and if the minor comments I had get addresses, I think it should be merged.
There are various open PRs and issues asking for Dart, LESS, and SCSS - these could be added as external filetypes. There should be no problem using C lexer for Dart and CSS lexer for LESS/SCSS (the CSS lexer supports LESS/SCSS modes).

What do you think?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.