| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reduce each one to target only the dotfiles specifically for that shell,
as opposed to previously where for example the `check-sh` target was
checking shell shims in for `mpd` and `plenv`.
I'm still not completely sure that's the right approach, but it's at
least less conceptually muddy than what we had before.
Notably, the check and lint for Korn shell includes a single POSIX shell
script file in its `shrc.d` subdirectory, so that check is executed
separately.
|
|
|
|
| |
This is a little bit clearer and nicer to read, I think.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This applies the same stable approach to testing the actual built
games that are shebannged with #!/bin/sh as has been applied to the
shell scripts in the `check-bin` and `lint-bin` targets.
There are no GNU Bash games in these directories, so the latter block of
code from the `bin` analogues to check or lint those is not needed.
The same applies here; this is not as complete a checking or linting of
the games directory as it could be; ideally we would check the sed(1)
and awk(1) scripts too.
|
|
|
|
|
|
| |
Both blocks are analogues of the POSIX checks, but are wrapped in a
conditional so that bash(1) doesn't become a hard dependency of the
default `make install` target.
|
|
|
|
|
| |
We haven't checked all of the shell scripts, just the POSIX sh ones,
which at present, is all but one of them; han(1df).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the `$(BINS)` target a prerequisite of `check-bin` so that all of
the scripts with a #!/bin/sh shebang are built, and then check them all
by iterating through a glob (and hence an order according to LC_COLLATE)
and stripping the `.sh` suffix to find the name of the matching
shebanged script.
Leverage `shellcheck`'s support of multiple check arguments to build an
argument list of the binscripts first before passing all of those to a
single call, simply for speed.
We don't have anything in this target to test the scripts of any other
type, such as the `.awk` or `.sed` scripts. `gawk` has a `--lint` mode
that might apply.
|
| |
|
|
|
|
| |
I never use it
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
As part of a foray into more active use of ksh and derivatives.
|
|
|
|
|
|
| |
I know almost nothing about Yash yet, but reading the manual page on its
startup behaviour implies a little coaxing is necessary to make it play
nicely with my file layout.
|
| |
|
| |
|
| |
|
|
|
|
| |
This probably contains a few mistakes
|
| |
|
|
|
|
|
| |
Also require flag files in ~/.welcome for displaying or not displaying
login stuff
|
|
|
|
| |
Quote a string entirely to appease shellcheck too
|
| |
|
| |
|
| |
|
|
Mostly to make way for an actual test suite beyond mere syntax checking
|