Does anyone knows, why shellcheck doesn't care about sourcing here:

but complaining here?

Does anyone knows, why shellcheck doesn't care about sourcing here:

docker-mailserver/target/bin/listmailuser

Line 7 in c7dec1e

. /etc/dms-settings 2> /dev/null

but complaining here?

A very good question, I have no idea :D

Does anyone knows, why shellcheck doesn't care about sourcing here:

It seems this was missed during review:

--source-path="${SCRIPT_DIR}" is probably what was intended as that's defined earlier in the script. No reference of SCRIPTDIR anywhere.

What I do find odd though is why the errors are reduced with that, but substituting the value with say x instead did not have the same effect but should be just as invalid 😕

EDIT: Nope, nevermind SCRIPTDIR is a special value for shellcheck (Might be worth documenting that link in the lint.sh file actually 😅 ). Without that you will get the failure for listmailuser as well among others such as the last var in start-mailserver.sh VARS list/section.

Which might hint that it's a similar behaviour with . /etc/dms-settings, it only reports the last occurrence for whatever reason.. In my common.bash PR, you'll see that the bounced spam test update adds a shellcheck disable comment only to the 2nd test case, without needing to do it for the first one despite no difference apart from declaration/source order in the file.

among others such as the last var in start-mailserver.sh VARS list/section.

I was wondering about this also some time ago 😆