First of all, Geany is a volunteer project, "plans" only exist in the minds of those who contribute. Support for any specific use-case needs someone to contribute it, so its not "surprising" that it has less support for web front end development if nobody has contributed it.

Also as Geany is written in C, most of the contributors are C programmers, so they can have problems understanding requirements for support for the non-C languages, and humans tend to reject what they don't understand, even improvements for C++.

For tags files, Geany now reads ctags format files, and might soon transition to the ctags library to do so, see #3049. So any tool that generates compliant ctags format should be usable after that is merged. There are lots of tags files on the wiki including Js and Jquery.

Geany supports about 60 programming languages and 10 markups, shipping tags for all the languages and standard and popular libraries would be huge, the tags automatically included are mostly those for Geany development (C, HTML & Php for Geany website) and ones that snuck in in pre-history and are retained for backwards compatibility. The same argument goes for included snippets.

Anybody can contribute to the wiki (just be patient with the account approval bot, its a human so it may be slow :-), just don't overwrite existing contributions, even if you think yours are better for the same thing, just add them as additional, overwrites may be reverted.

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