<blockquote>
<p>I couldn't find an answer, other than you're thinking it's unnecessary.</p>
</blockquote>

<p>I summarized the points from <a href="https://github.com/geany/geany/pull/1233" class="issue-link js-issue-link" data-url="https://github.com/geany/geany/issues/1233" data-id="177386393" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#1233</a> again in the part you quoted there. But to repeat from that PR:</p>

<blockquote>
<blockquote>
<p>Also proxy plugins matching blindly against extensions, without checking the file contents, are basically broken already since all the plugins are only allowed in a single directory and the likelihood of extension clashes is great.</p>

<p>Further, proxy plugins that register more than one extension will most likely have to discriminate between extensions in their probe() function anyway.</p>
</blockquote>
</blockquote>

<p>But if you think it's useful to pre-filter by extension, then why limit it to caseless, single-dot extensions?</p>

<blockquote>
<p>it just seems overkill at this point</p>
</blockquote>

<p>Again, please describe what you mean by overkill (In what sense? "too flexible"? "too much code"? "too much CPU/memory overhead"? etc), it's not clear from the context what you mean. As I mentioned previously, it's actually less code, is no more complex, fixes the caselessness problem, supports multi-dot extensions, and allows various other simple patterns.</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/1236#issuecomment-253818551">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ22dBS9VXlD6SUF11PAHpzJtuZhfks5qz5O3gaJpZM4J_6i1">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ-IdnUcB_3LUnx-1cNDxpXYjfovJks5qz5O3gaJpZM4J_6i1.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/1236#issuecomment-253818551"></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 #1236: \u003e I couldn't find an answer, other than you're thinking it's unnecessary.\r\n\r\nI summarized the points from #1233 again in the part you quoted there. But to repeat from that PR:\r\n\r\n\u003e\u003e Also proxy plugins matching blindly against extensions, without checking the file contents, are basically broken already since all the plugins are only allowed in a single directory and the likelihood of extension clashes is great.\r\n\r\n\u003e\u003e Further, proxy plugins that register more than one extension will most likely have to discriminate between extensions in their probe() function anyway.\r\n\r\nBut if you think it's useful to pre-filter by extension, then why limit it to caseless, single-dot extensions?\r\n\r\n\u003e it just seems overkill at this point\r\n\r\nAgain, please describe what you mean by overkill (In what sense? \"too flexible\"? \"too much code\"? \"too much CPU/memory overhead\"? etc), it's not clear from the context what you mean. As I mentioned previously, it's actually less code, is no more complex, fixes the caselessness problem, supports multi-dot extensions, and allows various other simple patterns."}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1236#issuecomment-253818551"}}}</script>