This seems to fix it, not sure it's perfect though:
```diff
diff --git a/ctags/parsers/typescript.c b/ctags/parsers/typescript.c
index 7dcc338ef..3fcd956a8 100644
--- a/ctags/parsers/typescript.c
+++ b/ctags/parsers/typescript.c
@@ -1820,8 +1820,11 @@ static void parseClassBody (const int scope,
Playing a tad with it, I see it's the `()`s in the members initialization (e.g.
`singletons.getSoundManager()`): if you remove the `()`s it keeps on parsing.
Now somebody will have to fix it… :slightly_smiling_face:
--
Reply to this email directly or view it on GitHub:
Sorry, I didn't answer sooner. The two files that I used as examples are
located here:
-
[User.ts](https://github.com/arianne/stendhal/blob/master/srcjs/stendhal/entity/User.ts)
-
[Player.ts](https://github.com/arianne/stendhal/blob/master/srcjs/stendhal/entity/Player.ts)
> ...see whether
> I don't see this as a particularly bad
No, its not ...
> few specifics hard-coded for the languages we have to
... just that you can't do that ATM without a hard coded filetype. Which is
why I asked the question, not knowing that the parser was a freebie thrown in
by @techee, not added by
> 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
> 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.
This is because there was no typescript parser originally and I added it in the
final "ctags sync" PRs but I did it in a lazy way only.
--
Reply to
> No, it's using the ctags parser language name
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.
@AntumDeluge to
@elextr
> Typescript is not a [built-in
> filetypes](https://github.com/geany/geany/blob/2509e21526d36034f5251381a76555e7300fbfc0/src/filetypes.c#L127)
> so how does it get called, I thought the lexer and parser names in a custom
> filetype had to be existing built-in names?
No, it's using
@AntumDeluge Hum, could you share your problematic file(s)? Or even better,
see whether [universal-ctags](/universal-ctags/ctags) has the same issue, and
report it there, as we're basically bundling those.
Anyway it's hard to tell what the issue could be, it probably comes from
something above
@techee (sorry to ping you again, but you are __the__ expert in tags and
parsers and symbols etc)
There is a ctags typescript parser being built into Geany.
But the Typescript filetype is a custom filetype that references a
10 matches
Mail list logo
