Casey Rodarmor

Yah, I thnk @laniakea64 is right, matching on strings is most useful, since for bools there's if / else. To keep the initial feature simple, I would skip bothering to...

I think that would probably be confusing, and using an additional attribute for the extension isn't much of a burden. But note that an extension is only required if the...

Also, one more reason for not stabilizing the `[script]` annotation right away: Since this is a new attribute, while it is unstable it is possible in a backwards compatible way...

@g9wp This seems unrelated to the `[script]` attribute.

@RoloEdits Good catch! I think I would lean heavily towards not allowing both `#!` and `[script]`. Having two potentially conflicting interpreters is rather confusing. Ideally the syntax highlighters would learn...

I would love to move the functionality of `cygpath` into `just` itself. However I can't really provide any pointers, since I'm not sure how `cygpath` works. In particular, I don't...

@casey There isn't, unfortunately. For the shell, we have the `windows-shell` setting, but nothing equivalent for the script-interpreter. We should either add `windows-script-interpreter` as as separate setting or make it...

Unfortunately I'm not actively working on this, it's a monster PR and I started it but let it get out of date and now there are a bunch of merge...

Closing, since I'm not making progress on this.

This is an annoying consequence of the way that the various dotenv settings work. Setting any `dotenv-` setting turns on dotenv loading, which uses *both* `dotenv-filename` and `dotenv-path`. `dotenv-filename` defaults...