Vidar Holen

Sorry, I have very little context for this. Can it simply push the same image instead of building a second one? Seems like that would be faster and easier to...

This is indeed an interesting case. It's not a useless use of echo, but more similar to concatenation of arrays (like `var=${array[@]}`). I don't have any great ideas for making...

You're right, this is due to ShellCheck's naive replacement of `` `..` `` with `$(..)` without considering that the `..` might be a redundant explicit subshell `(..)` causing the expression...

I can reproduce what I'm guessing is the same issue on x86_64 linux by running with QEmu usermode emulation. It does not seem to play well with the GHC runtime...

How do you even come across these things O___o

It's not entirely straight forward because `.shellcheckrc` files are per-file while the formatter options are per invocation. For example, you can do echo "disable=SC2034 # Don't warn about unused variables"...

This is a very interesting issue that ShellCheck should be warning about. Yes, it's a mathematically undecidable problem, but that's easily solved through the magic of false positives :P

Global variables are conventionally in all uppercase (`PATH, DISPLAY, SSH_CLIENT`, etc). For this reason, ShellCheck generally doesn't warn when using undefined uppercase variables. The best solution would probably be for...

I ran into the same issue with a library set `FLAGS_verbosity` style variables. How about a flag for setting a pattern/regex to ignore? This would let you do something like...

You're right, this is confusing. ShellCheck currently only supports targeting shells, and has no notion of the particular userland. When you specify `#!/bin/sh`, ShellCheck assumes (perhaps too zealously) that you...