Vidar Holen

Sounds good! Don't worry too much about threading it through into the right places, I can help out with that. The main thing is a function in `IO` that takes...

I haven't had a chance to look deeply into your changes yet, but here are my thoughts for plumbing: https://github.com/koalaman/shellcheck/commit/0138a6fafcbf107583753d87710f29cdebf7a80f This adds a function `siGetPortageVariables` to ShellCheck's SystemInterface, which is...

Thanks! I managed to get a Gentoo environment running in Docker, and got a bit further on this in https://github.com/koalaman/shellcheck/tree/ebuild It now runs end-to-end, but I ended up reverting a...

It's been a busy September, but https://github.com/koalaman/shellcheck/tree/ebuild now has most of the changes from the original patch, and I replaced the lovely attoparsec code with some janky regex matching and...

I see. So, I guess there are two surmountable issues: * Support for multiple levels of inheritance * Support for `@VARIABLE` and maybe `@USER_VARIABLE` in addition to `@ECLASS_VARIABLE` And some...

That would make sense. ShellCheck does already look at the script's closest parent directory with a `.shellcheckrc`, but that doesn't seem to help in your case.

Sounds useful. There are cases like `separator='======'; echo "$separator"` where the warning is provably not useful (the codebase makes this kind of analysis difficult atm), and some edge cases like...

As in a real script you can use a directive, `# shellcheck enable=all`, though it's obviously not a very discoverable feature on the website.

ShellCheck follows the convention that uppercase variables are shell/environment variables while lowercase ones are internal: ``` $ cat foo.sh #! /bin/sh echo "$var and $VAR" $ shellcheck foo.sh In foo.sh...

One of the major purposes of the wiki is to serve as an errata, so I really don't want it hard-coded into the binary. Just a couple of weeks ago...