I'm not sure how robust our parser is against invalid input
I wrote most of it, it ought to be perfect 😁
or updated ctags file format
In theory the format is perfectly well defined and stable (just adding new extension fields), so it should be fine™. But in practice uctags added support for escape sequences, which our parser doesn't understand, so it isn't.
so better use the upstream version of the official library to parse ctags files so we don't have to worry about this.
Yeah, it's a very large diff, but I guess using the canonical implementation is worth the extra copy.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.