<blockquote>
<p>From previous discussions, I think the suggestion (consensus?) was that for resources like markers, indicators and such, it would be best for Geany to manage and allocate these for the plugins so that each plugin doesn't try and use the same indices.</p>
</blockquote>
<p>Yes, and thats what I argued in the past too, but my problem is that Geany can only handle "first come first served" which might work for markers, but isn't so wonderful for build commands.</p>
<blockquote>
<p>From the filetype plugin discussions, I think the idea was that plugins would "register" themselves as handling a particular filetype</p>
</blockquote>
<p>Yeah thats certainly the ideal approach, but we are a long way from that ATM.</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-plugins/issues/733#issuecomment-380303571">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ-FVWV1NXKefWLDpWWvFYr8onB9qks5tnWXcgaJpZM4TNXBD">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJ6oxB1brKXj1ZzIV9UVDxgJYdjgxks5tnWXcgaJpZM4TNXBD.gif" height="1" width="1" alt="" /></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-plugins/issues/733#issuecomment-380303571"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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-plugins","title":"geany/geany-plugins","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-plugins"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #733: \u003e From previous discussions, I think the suggestion (consensus?) was that for resources like markers, indicators and such, it would be best for Geany to manage and allocate these for the plugins so that each plugin doesn't try and use the same indices.\r\n\r\nYes, and thats what I argued in the past too, but my problem is that Geany can only handle \"first come first served\" which might work for markers, but isn't so wonderful for build commands.\r\n\r\n\u003e From the filetype plugin discussions, I think the idea was that plugins would \"register\" themselves as handling a particular filetype\r\n\r\nYeah thats certainly the ideal approach, but we are a long way from that ATM."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany-plugins/issues/733#issuecomment-380303571"}}}</script>