<p>I would use this feature but I'm not fond of putting a preference in the main UI like that. It would probably fit better in a plugin preferences tab.</p>
<p>More importantly though I think it would be hard to implement cleanly/easily as the core of Geany would have to try and let plugins handle going to definition and if none did then it would have to fall back to the original behaviour. This sort of sound like the "providers" API that was previously discussed for plugins <a href="https://www.mail-archive.com/devel@lists.geany.org/msg02841.html">on the mailing list</a> (TLDR; allowing plugins to hook in to builtin features like this).</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/1394#issuecomment-280217547">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ2_twsNLC78P56c_TL8YVIgDRGYLks5rc7z1gaJpZM4MBr-x">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ4rezf5BWzq7FJp4SzAcTrbXri2vks5rc7z1gaJpZM4MBr-x.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/issues/1394#issuecomment-280217547"></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","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 #1394: I would use this feature but I'm not fond of putting a preference in the main UI like that. It would probably fit better in a plugin preferences tab. \r\n\r\nMore importantly though I think it would be hard to implement cleanly/easily as the core of Geany would have to try and let plugins handle going to definition and if none did then it would have to fall back to the original behaviour. This sort of sound like the \"providers\" API that was previously discussed for plugins [on the mailing list](https://www.mail-archive.com/devel@lists.geany.org/msg02841.html) (TLDR; allowing plugins to hook in to builtin features like this)."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1394#issuecomment-280217547"}}}</script>