I updated today from 3.0 to 3.1.
It appears that some of the bash comments are not parsed correctly.
Unfortunalety, I am not allowed to show code, so, I can help with the following only:
Code is ~750 lines long.
There is a ~ 308 lines function that its brackets cannot be highlighted by BracketHighlighter (disabling the plugin does not affect).
Writing a comment immediately before closing the brackets, it gets parsed correctly, afterwards it doesn’t. Regardless of indentation
The interesting thing is that from this code:
# >> >(tee test) 2>> >(tee test)3
# shellcheck disable=SCXXXX,SCXXXX
# ENV=SET command \
# > >(tee test) 2> >(tee test >&2) ; moar-command
only the last line is parsed as a comment, wherever placed on the file. Before, or after said brackets.
If I Ctrl+Shift+V paste (i.e. taking indentation into account) on the outermost level, only the first line is not parsed as a comment (all others are) - regardless of location in the file.
This kind of comment
shift # past argument
is recognised everywhere correctly.