Documentation
¶
Overview ¶
Command wild parses the shell scripts installed on this machine and reports the ones this parser cannot read.
It reads and never runs: the reference shell is consulted with `-n`, and nothing here executes a script. That is what makes it safe to point at /usr/bin.
It is a report and not a gate, for the same reason `make conformance` is one: the answer depends on what happens to be installed, so it cannot be the same twice on two machines. What it is good at is finding the questions nobody thought to put in the corpus.
It sweeps two populations and names both. The installed programs under /bin, /etc and the package manager's trees are what -dirs holds; the plugin and framework trees a shell sources at startup are configured in SH_WILD_DIRS, because their location is one machine's and no default could be right. The second is where every daily-driver construct found so far lived, and its absence is printed rather than passed over: "0 failures" over a population that was never looked at is the reading this report has to make impossible.
Source Files