<blockquote>
<p>But in Geany we already have fine tune settings for autocompletion. And if extrenal autocompletion will be implemented as substitution of internal autocompletion function it will be more comfortably to use.</p>
</blockquote>
<p>I would strongly suggest that the plugin should be shown to work first, before you worry about interacting with settings in Geany.</p>
<p>Making the communication with the language server work, without blocking Geany, and fast enough, is possibly going to be a challenge.  And you have to handle the user typing fast enough that the server hasn't replied when you get the next <code>editor-notify</code> signal, unlike your dlang plugin which uses a library version of the d compiler IIUC (similar to <a class="user-mention" data-hovercard-user-id="181177" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/codebrainz">@codebrainz</a> use of clanglib) and so is blocking which makes life simple.</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/1854#issuecomment-387029285">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ7OcIU9vfJoUdx9tKcCWgf3nQtxoks5twCdTgaJpZM4Tz9fX">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJ2UAf2ga-z0Wvct-DCEaLoMu_Fthks5twCdTgaJpZM4Tz9fX.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/issues/1854#issuecomment-387029285"></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":"@elextr in #1854: \u003e But in Geany we already have fine tune settings for autocompletion. And if extrenal autocompletion will be implemented as substitution of internal autocompletion function it will be more comfortably to use.\r\n\r\nI would strongly suggest that the plugin should be shown to work first, before you worry about interacting with settings in Geany.\r\n\r\nMaking the communication with the language server work, without blocking Geany, and fast enough, is possibly going to be a challenge.  And you have to handle the user typing fast enough that the server hasn't replied when you get the next `editor-notify` signal, unlike your dlang plugin which uses a library version of the d compiler IIUC (similar to @codebrainz use of clanglib) and so is blocking which makes life simple."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1854#issuecomment-387029285"}}}</script>