<p>I don't doubt it has extra value, much like a Qt filetype which would have "keywords" like <code>slots</code>, <code>signals</code>, <code>emit</code> and build commands for <code>moc</code> and <code>uic</code>. I'm really only questioning where we draw the line on adding custom filetypes. Like the assembly examples I gave above, each would have its own set of mnemonics and assemblers, but IMO in that case it is too much to ship by default.</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/1339#issuecomment-267208852">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ3psiZbaAwFgRhBgfHcXEN1DTaA-ks5rIJXkgaJpZM4LNiiE">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ6Yfe81lyDrdzezjE4dKYyUzZBp-ks5rIJXkgaJpZM4LNiiE.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/pull/1339#issuecomment-267208852"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<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://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@codebrainz in #1339: I don't doubt it has extra value, much like a Qt filetype which would have \"keywords\" like `slots`, `signals`, `emit` and build commands for `moc` and `uic`. I'm really only questioning where we draw the line on adding custom filetypes. Like the assembly examples I gave above, each would have its own set of mnemonics and assemblers, but IMO in that case it is too much to ship by default."}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1339#issuecomment-267208852"}}}</script>