Jacob Deichert

Hmmm, i like that idea. That would make it very easy to tell what's optional and what's not.

> I would suggest following traditional shell syntax for brackets: [optional] Yeah, agree that sticking with traditional shell syntax is better – going to go with [optional] instead of (optional?)...

> it will be good if we can provide default value Maybe like this: `[optional=default_value]` ? Still thinking about this... named flags don't have support for a default value yet...

> Could also do traditional shell syntax for mandatory args: `` as opposed to current `(required)` Yeah, I originally had that but then changed it in #16 because a few...

Hey! Glad you're enjoying mask. `just` was one of my inspirations :) So one option you have available is starting all your commands with bash in the background using `&`....

So I currently work around this by sourcing an env file whenever I need it: ```markdown ## build ~~~bash source "$MASKFILE_DIR/.env" echo $WHATEVER_VAR ~~~ ``` But I do see a...

I just thought of a 4th option which I believe is better than options 2 & 3 and is more flexible. Mask could look for a top-level code block that...

Hey, thanks for reporting this. Mask only checks for "powershell". Because it doesn't recognize "pwsh", it tries to fall back to assuming that command is on the system I think....

Yeah we can probably add some way to skip code blocks if the system doesn't have the expected executor installed. In general, I think that may lead to a bad...

> Maybe mask could also print that the executor is missing and that it's using the other one just to let the user know. The next release of mask will...