`if [[ $(type -t "editions_${OS}") == function ]]; then`
showing this line as function in symbols, even it isn't really function. Wasn't like that in older version
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 ;-)
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.
Same problem when using empty array literals. (bash) Geany built from debian sid source package 2.0-2. (Patches only affect iniconf parser)
@kujub this has already been fixed in current development version (see #3859). The OP issue hasn't, though.
@b4n OK, that's nice! Latest release was from Oct 19, 2023 anyways. Maybe there will be a new one soon...?
github-comments@lists.geany.org