<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=793526" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/b4n">@b4n</a>, 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).</p>
<p>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.</p>
<p>Certainly more heavily integrated languages with lexers and parsers that need more support should be considered carefully, but one config file seems low impact.</p>
<p>However as there are already too many programming languages, maybe we need another group in filetypes.extensions, but thats another issue (<a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="408414274" data-permission-text="Issue title is private" data-url="https://github.com/geany/geany/issues/2087" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/2087/hovercard" href="https://github.com/geany/geany/issues/2087">#2087</a> actually :).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/pull/2085#issuecomment-462028243">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ6OwhR8hEWJjbgahQZiUVSZibDxZks5vLpJbgaJpZM4anw0r">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJyOOe3bRMriocxGcMkhjB7HGGeHdks5vLpJbgaJpZM4anw0r.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #2085: @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).\r\n\r\nBut 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.\r\n\r\nCertainly more heavily integrated languages with lexers and parsers that need more support should be considered carefully, but one config file seems low impact.\r\n\r\nHowever as there are already too many programming languages, maybe we need another group in filetypes.extensions, but thats another issue (#2087 actually :)."}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/2085#issuecomment-462028243"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/pull/2085#issuecomment-462028243",
"url": "https://github.com/geany/geany/pull/2085#issuecomment-462028243",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>