Add Nim filetype #2085
b4n left a comment
Looks reasonable, but do we want Nim builtin? I don't mind, but for not very widespread languages that only need/have a custom filetype, we often just have a wiki page. However, if the filetype is of sufficient quality I guess we can have it in, especially as I read a few mentions of Nim lately here and at Universal-CTags so it might be gaining popularity.
@b4n, a quick survey shows Nim doesn't make it near the top of any of the programming language rankings, its no typescript or coffeescript or other high profile JS languages (as flawed these lists are, not making any is likely significant).
But whilst in the past I have also tended to suggest the wiki I have sort of changed my mind a bit, really should Geany (or other tools) be picking winners, especially when it is only a filetypes.XXX.conf file. Its unlikely to need much support effort at that level.
Certainly more heavily integrated languages with lexers and parsers that need more support should be considered carefully, but one config file seems low impact.
However as there are already too many programming languages, maybe we need another group in filetypes.extensions, but thats another issue (#2087 actually :).