> So can't we just make it a shallow shim over glib instead of including the > ctags one?
Probably we could make some wrapper around it but there are minor semantic differences between the APIs which are easy to miss and which we probably won't notice in the future when something in upstream uctags changes and we just grab the sources from there. All the parsers upstream from the "parsers" directory are non-regex ones and the regex ones are only those from https://github.com/universal-ctags/ctags/tree/master/optlib but none of the languages seem too interesting for Geany (we have a hand-written markdown parser). So we won't miss much from the upstream by killing the regex parser support. So the only problem are Actionscript and Cobol parsers. As I said, personally, I would drop them. But the second best solution would be rewriting them as non-regex parsers (but preferably not by me - @b4n you said something like it would be fun rewriting those - I would really hate myself for stealing the fun from you :-) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2018#issuecomment-454124079
