<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=713965" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/techee">@techee</a>  <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=77077" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/masatake">@masatake</a>  <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=793526" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/b4n">@b4n</a></p>
<p>I assume you are talking about having u-ctags provide a library that other apps can use?  Thats a good idea. Why not refactor u-ctags to separate the parsers and parsing infrastructure from the command line and file writing stuff.  That way such a library only includes parsing, thats the part most apps want and the library can be used by the u-ctags app of course :).</p>
<p>As I think <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=713965" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/techee">@techee</a> proposed apps (including u-ctags itself) should register functions to provide things like reading files and accepting tags, for u-ctags to write to disk (I presume) and for Geany to add to symbols.</p>
<p>Also apps need to be able to not build in parsers for languages they don't want, there are twice as many files in u-ctags/parsers as in Geany/parsers directory.</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-486472477">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ36YBKGIR4JMS32H5DPSDZQBANCNFSM4HEAA74Q">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAIOWJZHS7LNBGSHL7N2BTDPSDZQBANCNFSM4HEAA74Q.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":"@elextr in #2119: @techee  @masatake  @b4n \r\n\r\nI assume you are talking about having u-ctags provide a library that other apps can use?  Thats a good idea. Why not refactor u-ctags to separate the parsers and parsing infrastructure from the command line and file writing stuff.  That way such a library only includes parsing, thats the part most apps want and the library can be used by the u-ctags app of course :).  \r\n\r\nAs I think @techee proposed apps (including u-ctags itself) should register functions to provide things like reading files and accepting tags, for u-ctags to write to disk (I presume) and for Geany to add to symbols.\r\n\r\nAlso apps need to be able to not build in parsers for languages they don't want, there are twice as many files in u-ctags/parsers as in Geany/parsers directory."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2119#issuecomment-486472477"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2119#issuecomment-486472477",
"url": "https://github.com/geany/geany/issues/2119#issuecomment-486472477",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>