<p></p>
<blockquote>
<p dir="auto">Of the first list the only one I would suspect may have been modified in Geany independent of ctags is Lua.</p>
</blockquote>
<blockquote>
<p dir="auto">Of the second list I'm pretty sure Verilog and VHDL were added to ctags then brought into Geany but probably have > developed from that initial version so the ctags version should be good.</p>
</blockquote>
<p dir="auto">Thanks, let's see if others have some more information.</p>
<blockquote>
<p dir="auto">c.c -- runs screaming from the room. If languages in c.c have separate parsers in ctags we should import them instead (eg the new c/c++ parser) and only keep c.c for those languages that do not have ctags parsers (if any).</p>
</blockquote>
<p dir="auto">After <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1046096123" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2984" data-hovercard-type="pull_request" data-hovercard-url="/geany/geany/pull/2984/hovercard" href="https://github.com/geany/geany/pull/2984">#2984</a> is merged, I'd like to open a pull request switching us to the new c/c++ parser from uctags so these 2 most terrible languages (parsing-wise) should be eliminated from c.c. The rest of course remains. I remember the pre-babies version of Colomban talking about about separating those parsers from c.c but I suspect this task is delayed by about 15 years now ;-).</p>
<p dir="auto">Anyway, the purpose of this PR is to switch to those parsers where we know we can just grab the uctag version - we'll have to deal with the rest later parser by parser.</p>
<blockquote>
<p dir="auto">I presume that any parser not in the lists is the same in both Geany and ctags so won't need updating?</p>
</blockquote>
<p dir="auto">Those with minimal or no changes are in PR <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1047808770" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2990" data-hovercard-type="pull_request" data-hovercard-url="/geany/geany/pull/2990/hovercard" href="https://github.com/geany/geany/pull/2990">#2990</a></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/2991#issuecomment-964017564">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ4O65N357WZ7RY3SC3ULDZ4NANCNFSM5HTSAKMA">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<img src="https://github.com/notifications/beacon/AAIOWJ5VMJKQQ3XC3T3A7K3ULDZ4NA5CNFSM5HTSAKMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHF233HA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/pull/2991#issuecomment-964017564",
"url": "https://github.com/geany/geany/pull/2991#issuecomment-964017564",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>