> Oh ok, but having added a parser I wonder why the creator of the Typescript > filetype didn't go the whole hog and make a built-in filetype. Then they > could customise all the language dependent code scattered throughout Geany.
I don't see this as a particularly bad, actually if we could get most, if not all, filetypes uses a declarative style and only have the few specifics hard-coded for the languages we have to, I wouldn't find that too bad. And with the shift towards Scintilla's named-only lexer API, things will shift towards named stuff. If course, we'll probably need magic constants still to optimize several checks for the hard-coded bits, but that could be a bonus a few VIP names get. We're surely not here yet, but I'm not sure it's a bad slope to lean on. And if there's nothing specific this filetype would need hard-coded, I don't see no harm -- actually, just less code, and you know I love less code :wink: -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3416#issuecomment-1447866846 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/3416/1447866...@github.com>
