Matthew Lyon

What are some general use cases for this? It's fairly easy to have your own custom type definitions alongside your config, see: https://github.com/mattly/dotfiles/blob/89a9831a07ba42a20d2cb765ec1df78dada43829/bork/_mac_dev_basics.sh#L30 and https://github.com/mattly/dotfiles/blob/89a9831a07ba42a20d2cb765ec1df78dada43829/bork/types/npm-config.sh

Well, macOS uses the BSD utils. Right? Maybe they've got their own variants now that are different, I haven't been keeping up with things.

from what I can remember and what I can read, `check_failed` was created for the `check` type (which is basically a way of hooking arbitrary expressions into the `ok` system)...

I don't remember what use case my initial stab at `download` was intending to solve, but I can 100% guarantee you it had a `Content-Length` header :p. I think you...

indeed. I know what the problem is but I'm unsure how to go about solving it. I have a failing test case to start with though. I have a feeling...

I should note that this *only* solves the problem with bake, it doesn't solve the problem with `ok`. 😿

I fixed `ok`, but now it comes down to making sure everything is escaped properly in each of the types. I did that for git and github and updated the...

Thanks; I had thought `-y` was synonymous with `--yes` (which I'm using), but I'll look at that. I had found another solution involving debconf that I should document too.

hm... I think what we need is some use cases, shell scripts to pass those cases, and then an idealized form of what those would look like in bork.

one issue here is that some scripts (f.e. "ok brew" when installing) NEED to send their output because they also need input. Perhaps the types will have to respect the...