> I've tried to compile the forth.c generated from forth.ctags and I got a > compilation error in geany, then I supposed that it was because the ctags > code was out of date in geany.
Yes, we are like two years behind I'm afraid :-(. In general we want to make an update to the latest ctags early after every release and keep this ctags version until the next release. The problem is that our 3-times-a-year Geany release cycle degraded slightly ;-). > Then I've synchronised the geany code with the latest ctags, this time it > compiled without singificant error (if I remember well), but the resulting > geany binary didn't load at all (and didn't crash either). There are always some surprises that have to be solved after updating to the newest ctags version. In general, you always have to update the mappings in https://github.com/geany/geany/blob/master/src/tagmanager/tm_parser.c for all parser - if there's a mismatch, Geany will print an error telling you in which mapping the problem is and won't load. Anyway, if I'm not wrong, optlib parsers exist for quite some time so if you just check out an older ctags version which roughly corresponds to the last ctags update we did in Geany and generate the source of the parser using that version, you should be able to compile it with Geany. Then check some of the recent open (or closed) PRs adding a filetype support in Geany to see how to integrate the new parser to Geany. Also check the HACKING file, I'm just afraid that the most up-to-date version is part of not-yet-merged https://github.com/geany/geany/pull/3169. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3557#issuecomment-1715899834 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/3557/[email protected]>
