[Github-comments] Re: [geany/geany] wrong functions showed in symbols (Issue #3661)

[Colomban Wendling via Github-comments]

Current universal-ctags still suffers from the issue.

> Detecting command start might not be simple since they can be embedded.

It is not trivial indeed.  And the other solution of being stricter parsing 
`function …` is tricky as well because the syntax is actually fairly complex 
(e.g. `function @(cat)` is perfectly valid Bash -- just learnt that though).

I think this should be forwarded upstream anyway though.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3661#issuecomment-1786021865
You are receiving this because you are subscribed to this thread.

Message ID: 

[Github-comments] Re: [geany/geany] wrong functions showed in symbols (Issue #3661)

[elextr via Github-comments]

The `sh` parser was swapped to the ctags parser from the Geany one.

`function` and other keywords are actually only keywords at the start of a 
command (for bash and zsh at least).  But the ctags `sh` parser is pretty 
simple and does not track start of command.  Detecting command start might not 
be simple since they can be embedded.

That said there are some changes around `function` in the ctags parser that are 
newer than the one in Geany, but not sure if they will help.

 @techee maybe add `sh` to the list of parsers that need to be updated, 
especially to get the excellent work of @b4n ;-)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3661#issuecomment-1782082151
You are receiving this because you are subscribed to this thread.

Message ID: