Vidar Holen

Indeed. This is due to the naive check added way back in #86. I'd love to remove this hack all together and encourage people to trap with functions, but it's...

Unfortunately this kind of indirect assignment&expansion continues to be a pain point without a great solution.

@kurahaupo I like this idea. It's somewhat rare but it does happen: * https://github.com/tailscale/tailscale/blob/1007983159ca29ad1ba3ed8bc005ca8dc8b0f03a/logtail/example/logreprocess/demo.sh#L20 * https://github.com/minamarkham/formation/blob/70a331a4d440eb840a19f972602211ed9d18d374/slay#L7 * https://github.com/hyperledger/besu/blob/5e0301a749ac49a611a26c1df84eee5c0ee198f6/docker/tests/dgoss#L73 Plus some variations/attempts: * https://github.com/hubotio/hubot/blob/7795fe53fb1a3dde85537589149cab0f0b58404a/bin/e2e-test.sh#L7 * https://github.com/rkt/rkt/blob/171c416fac02516604e48d2e65153dd55a12513e/Documentation/examples/build-container/play-example/build-play-example.sh#L13 And equally interesting, some places...

There are some similar suggestions in #356. It may be that listing variables in a directive is ideal. Alternatives that work today include: * Explicitly declaring them without assigning: `export/declare...

I'm not sure about the logistics of managing a second set of IDs, but I definitely see how this would help the `disable` lines.

The simple reason that I'm not in any way affiliated with that project :P

I see the problem, though it's quite niche compared to the refactoring it would take. You can leave the issue open, but I think your best bet is to specify...

The warning is indeed confusing, but it does indicate a real problem. You should not use `[[ $(grep -q ..) ]]` because it has no output, and therefore will always...

@safinaskar Why do you use `set -e` at all in this example if you don't want to exit on non-zero command return statuses?

This is true in Bash 4, but not in Bash 3. ``` host1$ echo "$BASH_VERSION"; var='foo bar'; cat