I have a question, what do you think you will gain by having this in the Geany core, given that (AFAIK) none of the normal contributors normally have access to the toolset for the language, so we will not be able to support it much. So you will be maintaining it yourself anyway.

And given that it likely adds work for the Geany community of volunteers, what do they get out of it?

And given that it adds more code to everybodys copy of Geany, what do they get out of it?

On a practical note, as @codebrainz said on the mailing list, it is policy to have Scintilla lexers and ctags parsers added upstream first, Geany does not support its own copies (except historical ones). So you need to submit those parts upstream.

@ThibLind to explain where I'm coming from some more.

In these days of corporate supported open source (go, rust etc) and academic supported open source (Julia etc) and open source projects with complex organisations (Debian etc) Geany is somewhat of an anachronism. Geany is just a bunch of people contributing in their own, mostly limited, time (sorry for the delay in replying BTW) and as such they work on what they are interested in, and limited to what they have time to do.

This means that there is no specific acceptance process, any contributions are "accepted" if somebody reviews, tests and merges them. It also means that there is almost never an absolute rejection of a PR either, well unless people really don't like it, then they complain loudly, but for most everybody thinks "just because I'm not interested or don't have time now does not mean somebody else will not become interested or have time tomorrow" so nobody outright rejects anything that they do not totally hate.

So I just want to make sure that this is understood and acceptable when your contribution is coming from an organisation that may have its own goals and schedules.

Also there are costs of time and effort to initially review, install the toolchain, learn the language, test, and merge. So support for uncommon languages tends to be slow to be merged and tends to not happen if Scintilla has not accepted the lexer or uctags has not accepted the parser (where appropriate).

Also there is then the question of ongoing maintenance. Will your organisation commit to maintaining the Scintilla, tags and Geany parts and supporting user questions/requests/problem reports? Since as I said I don't know of any Geany contributors who use your language, so support from regular Geany contributors is likely to be limited.

All this is not to discourage you from continuing, just to make sure you understand ahead of time.

@ThibLind Suggestion: Add these custom files to the wiki, than Geany users can always optionally load this file, while you still can edit your own page.

example https://wiki.geany.org/config/scss