Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
But anyway it should be a separate PR, and maybe it could start a "filetype_specific.c" file and put it in a function there, and other language specific parts of Geany could be migrated over (a long) time.
Just for the info, we have this filetype_specific.c in TM now and it's called tm_parser.c. The only exception where it isn't used is this check
which is kind of constant so I thought it wouldn't be necessary to add a callback to tm_parser.c for this, the rest of TM doesn't contain any language-specific code.
I'm kind of proud I set an example here for the rest of the code and that in this area TM is is now better than the rest of Geany at least in something :-). These would be the the screenshots of "the most salient lines of code" for the last year if some idiot asked me to do something like that (not really, I'd be gone).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.