"external-sources=true" in my .shellcheckrc isn't working, but "-x" on the command line does

[djmills64]

For bugs

• Rule Id (if any, e.g. SC1000): 1091
• My shellcheck version (shellcheck --version or "online"): 0.7.0
• [ ] The rule's wiki page does not already cover this (e.g. https://shellcheck.net/wiki/SC2086)
• [ ] I tried on https://www.shellcheck.net/ and verified that this is still a problem on the latest commit

For new checks and feature suggestions

• [ ] https://www.shellcheck.net/ (i.e. the latest commit) currently gives no useful warnings about this
• [ ] I searched through https://github.com/koalaman/shellcheck/issues and didn't find anything related

Here's a snippet or screenshot that shows the problem:

$ shellcheck -x AddRole.sh

produces no output. But without the "-x" I get:

In AddRole.sh line 42:
. constants.sh
  ^----------^ SC1091: Not following: constants.sh was not specified as input (see shellcheck -x).

In AddRole.sh line 43:
. functions.sh
  ^----------^ SC1091: Not following: functions.sh was not specified as input (see shellcheck -x).

The .shellsheckrc file in the same directory contains:

# .shellcheckrc

external-sources=true
disable=SC2162

The "external-sources=true" line is not having the desired effect. The disable line is working - thus confirming that the file is used.

Here's what shellcheck currently says:

Here's what I wanted or expected to see:

[koalaman]

Unfortunately the external-sources directive is only supported in ShellCheck v0.8.0 and up!

[djmills64]

Thanks. It doesn't seem to be possible to specify multiple folders with "source-path="

I attempted to add a 2nd folder with a colon in between, but then neither folder works. Please advise if there's a way.

[djmills64]

Actually it looks like colon separated works on the command line, but from a .shellcheckrc file you seem to need multipe "source-path=" entries. If that is correct, please add to the documentation.