<p>Yeah, one of the mailing list threads listed in the "Related"  comment in <a href="https://github.com/geany/geany/issues/1195" class="issue-link js-issue-link" data-url="https://github.com/geany/geany/issues/1195" data-id="173359447" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#1195</a> would be more appropriate place than here.</p>

<p>My main objection to this PR is exposing more of TM to the plugin API, and doing so because of a single plugin language, for a single implementation, which has an already extremely common workaround mechanism builtin to the main implementation for just this case (C-extensions).</p>

<p>If I needed this in a GeanyPy plugin, I'd probably propose to add a helper function/API into it directly to smooth over the language barrier.</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/1187#issuecomment-243643261">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ8yXMcD9-WfDOkfz1qM2Xyu6bWPvks5qlOtHgaJpZM4JqVBL">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ_nhgkATpcKzd4h0o2H82KGVbchyks5qlOtHgaJpZM4JqVBL.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/1187#issuecomment-243643261"></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 #1187: Yeah, one of the mailing list threads listed in the \"Related\"  comment in #1195 would be more appropriate place than here.\r\n\r\nMy main objection to this PR is exposing more of TM to the plugin API, and doing so because of a single plugin language, for a single implementation, which has an already extremely common workaround mechanism builtin to the main implementation for just this case (C-extensions).\r\n\r\nIf I needed this in a GeanyPy plugin, I'd probably propose to add a helper function/API into it directly to smooth over the language barrier."}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1187#issuecomment-243643261"}}}</script>