<p>I haven't thought deeply on this, but for programing/scripting languages, one way could be to break them up in their general syntax style, for an incomplete example:</p>
<ul>
<li>
<p>Pascal-style</p>
<ul>
<li>Ada</li>
<li>Pascal</li>
<li>Coffeescript</li>
<li>Lua</li>
<li>Ruby</li>
</ul>
</li>
<li>
<p>C-style</p>
<ul>
<li>C</li>
<li>C++</li>
<li>C#</li>
<li>D</li>
<li>Go</li>
<li>JS</li>
<li>Java</li>
<li>Rust</li>
<li>Vala</li>
</ul>
</li>
<li>
<p>Python-style</p>
<ul>
<li>Python</li>
<li>Genie</li>
<li>Nim</li>
</ul>
</li>
<li>
<p>Lisp & Functional-style</p>
<ul>
<li>Lisp</li>
<li>Scheme</li>
<li>Clojure</li>
<li>Erlang</li>
<li>Haskell</li>
</ul>
</li>
</ul>
<p>It wouldn't be perfect, and the "C-style" group would have a lot of languages, but at least it's better than the incorrect/non-existent distinction of "Programming" vs "Scripting".</p>
<p>Another more obvious way would be to group them alphabetically, collapsing ranges of letters together where there aren't very many languages (to avoid a large 26 item menu with few items in each submenu).</p>
<p>Just a couple ideas.</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/issues/2087#issuecomment-462074889">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ3T8K7c9Afjk0N593CTXD3giHQ8Wks5vLymbgaJpZM4aydQv">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJw5UGR8-yWmDGA-GRSFm4syuT4R_ks5vLymbgaJpZM4aydQv.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":"@codebrainz in #2087: I haven't thought deeply on this, but for programing/scripting languages, one way could be to break them up in their general syntax style, for an incomplete example:\r\n\r\n* Pascal-style\r\n  - Ada\r\n  - Pascal\r\n  - Coffeescript\r\n  - Lua\r\n  - Ruby\r\n\r\n* C-style\r\n  - C\r\n  - C++\r\n  - C#\r\n  - D\r\n  - Go\r\n  - JS\r\n  - Java\r\n  - Rust\r\n  - Vala\r\n\r\n* Python-style\r\n  - Python\r\n  - Genie\r\n  - Nim\r\n\r\n* Lisp \u0026 Functional-style\r\n  - Lisp\r\n  - Scheme\r\n  - Clojure\r\n  - Erlang\r\n  - Haskell\r\n\r\nIt wouldn't be perfect, and the \"C-style\" group would have a lot of languages, but at least it's better than the incorrect/non-existent distinction of \"Programming\" vs \"Scripting\".\r\n\r\nAnother more obvious way would be to group them alphabetically, collapsing ranges of letters together where there aren't very many languages (to avoid a large 26 item menu with few items in each submenu).\r\n\r\nJust a couple ideas."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2087#issuecomment-462074889"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2087#issuecomment-462074889",
"url": "https://github.com/geany/geany/issues/2087#issuecomment-462074889",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>