Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
What does upstream say about the changes?
The change is in our sources, not the upstream ones.
What is the setting set to if the tag_parser= is not present?
For most languages the parser is hard-coded using the table here:
https://github.com/geany/geany/blob/ef2255bced523a3ad75773bac3e77b02725f10fd/src/filetypes.c#L116
I think only a few non-builtin filetypes like JSON use the tag_parser option to specify the parser by name. But if the name is invalid or not provided, we shouldn't crash which this PR tries to do.
And can tag_parser= mean that?
Mean what?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.