This is probably trivial to fix, but I’ve no idea where or how to do so. The following constructs break syntax highlighting:
FAIL1=$( anything-here sort --unique --ignore-case)
It appears that the code to detect the start of case blocks doesn’t correctly handle the string “case” being used within a block like this. Quoting it to make
FAIL1=$( anything-here sort --unique "--ignore-case")
does get highlighted correctly though.
FAIL2=${PACKAGESITE:-"String ${SOME_VARIABLE} more string"}
This took me a moment to trace down the actual fault.
As best I can follow, the syntax highlighting says that the } within the string is paired to the opening ${ and not the the nested one, so thus closes the string as well, so the following " is considered the start of a new string.
Make sense? Basically ${} inside “” inside ${} breaks the highlighting.