<blockquote>
<p>How about moving libctags code to u-ctags?</p>
</blockquote>
<p>Yeah, that's the plan. Actually there are very little changes needed now (try to diff the commit of uctags mentioned in <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="436850387" data-permission-text="Issue title is private" data-url="https://github.com/geany/geany/issues/2132" data-hovercard-type="pull_request" data-hovercard-url="/geany/geany/pull/2132/hovercard" href="https://github.com/geany/geany/pull/2132">#2132</a> against the Geany version from the pull request), we should just try to think about what's the right way to do it in uctags - the way we handle re-parsing might not be the best way from uctags point of view and it would probably be nicer to handle it using some new callback functions in writers.</p>
<p>I definitely want to work on it but only when we get Geany reasonably up-to-date. Even <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="436850387" data-permission-text="Issue title is private" data-url="https://github.com/geany/geany/issues/2132" data-hovercard-type="pull_request" data-hovercard-url="/geany/geany/pull/2132/hovercard" href="https://github.com/geany/geany/pull/2132">#2132</a> is against uctags which is several months old. But if it gets merged soon, I'd create one more commit to sync it against the most recent uctags version and then we can start thinking about bringing the needed functionality to uctags.</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/2119#issuecomment-486399229">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ2745FFZYYQOGC5CN3PSC2Q3ANCNFSM4HEAA74Q">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAIOWJ4TNSRJPXHFMDDMGFTPSC2Q3ANCNFSM4HEAA74Q.gif" height="1" width="1" alt="" /></p>
<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://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@techee in #2119: \u003e How about moving libctags code to u-ctags?\r\n\r\nYeah, that's the plan. Actually there are very little changes needed now (try to diff the commit of uctags mentioned in #2132 against the Geany version from the pull request), we should just try to think about what's the right way to do it in uctags - the way we handle re-parsing might not be the best way from uctags point of view and it would probably be nicer to handle it using some new callback functions in writers.\r\n\r\nI definitely want to work on it but only when we get Geany reasonably up-to-date. Even #2132 is against uctags which is several months old. But if it gets merged soon, I'd create one more commit to sync it against the most recent uctags version and then we can start thinking about bringing the needed functionality to uctags."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2119#issuecomment-486399229"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2119#issuecomment-486399229",
"url": "https://github.com/geany/geany/issues/2119#issuecomment-486399229",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>