Tako Schotanus

Yeah, same thing happened to my wife, she didn't understand that either and thought it was a bug in JBang. Thing is that I'm not sure she would have read...

> So here, we can clearly see that all flags are located before the command, but then: The issue here is that `jbang --help` doesn't actually tell you that doing...

> What's the likelihood Indeed. I'd even suggest: ``` or jbang run hello.java [args...] (to run a .java file) or jbang hello.java [args...] (to do the same but shorter) or...

Have you tried with `jbang wrapper install --force`?

Indeed, because the wrapper command should only update the local files. We could perhaps change the priority of the jar lookup: so if there is a local jar we use...

In fact, I think that a better option in every case. If somebody installs a wrapper using a certain jbang version we shouldn't decide to use a different one.

Hmmm, it already works that way. In fact I cannot reproduce the problem: ``` $ ../jbang-0.80.2/bin/jbang wrapper install $ ./jbang version 0.80.2 $ ../jbang-0.80.2.4/bin/jbang wrapper install --force $ ./jbang version...

Just to add the reasoning for my `platform::g:a:v@pom` suggestion: it's so we don't have to add a whole bunch of new CLI flags and jbang-catalog.json options for this. The feature...

It's just a very basic implementation right now. There's no validation yet, so you could for example create a `build.jbang` file without a `//SOURCES` line and that would probably fail...

> should we make this feature enabled only when --preview specified as we discussed? Sure, that's okay with me.