Adrian Cole

minimally we need to quote more. ex this: ```diff --- a/.bingo/Variables.mk +++ b/.bingo/Variables.mk @@ -21,23 +21,23 @@ GOIMPORTS := $(GOBIN)/goimports-v0.1.2 $(GOIMPORTS): $(BINGO_DIR)/goimports.mod @# Install binary/ries using Go 1.14+ build command....

I think spaces just won't work. there are a bunch of reasons why. windows would only work if you can use non-spaces for both go and the checked out project

one main issue is that `go env GOPATH` comes out like `c:\...' The result is this is ambiguous and fails ``` GOBIN ?= $(firstword $(subst :, ,${GOPATH}))/bin ```

This seems to work around things well enough in git bash assuming you have go installed in a non-spaced directory such as you'd get using https://github.com/travis-ci/gimme ```diff --- a/.bingo/Variables.mk +++...

I agree that re-using a version from go.mod would be the simplest and most likely to stay up to date. OTOH I also can understand this might be tricky, especially...

you can probably close this one out as that project has been dormant since sept 2020

hmm I think maybe the build is broke? I looked at travis and nothing ran last 5 months. I get some diff output errors locally even if I run in...

will be great to see this landed as it is surprising behavior without a fix. @jaimem88 let me know if you ran out of steam!

I think this also hits when help is default. Ex. if your app is named "foo", `foo` and `foo help` will trigger the unnecessarily arg validation

https://github.com/tetratelabs/wazero/tree/main/examples/gojs and also https://wazero.io/languages/ may help wazero just cut its first beta tag (v1.0.0-beta.1) and also opened a [gophers slack](https://gophers.slack.com/) `#wazero` channel for support, updates and conversation! Note: You may...