Would my utility simexec(1), which simulates program execution with a given argv, be useful as a part of Bonsai?
Usage: simexec [file] (command (arguments...))
This is useful for testing multi-program binaries and other things.
Would [my utility simexec(1)](https://git.sr.ht/~trinity/src/tree/main/item/simexec), which simulates program execution with a given argv, be useful as a part of Bonsai?
```
Usage: simexec [file] (command (arguments...))
```
This is useful for testing multi-program binaries and other things.
maybe not as a coreutil, but we could always use more tools in general under the bonsai name. what do you think about a set of tools specifically for testing à la GNU findutils?
(I know findutils contains some coreutils, but the same principle would be in effect)
maybe not as a coreutil, but we could always use more tools in general under the bonsai name. what do you think about a set of tools specifically for testing à la [GNU findutils](https://www.gnu.org/software/findutils/)?
(I know findutils contains some coreutils, but the same principle would be in effect)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Would my utility simexec(1), which simulates program execution with a given argv, be useful as a part of Bonsai?
This is useful for testing multi-program binaries and other things.
maybe not as a coreutil, but we could always use more tools in general under the bonsai name. what do you think about a set of tools specifically for testing à la GNU findutils?
(I know findutils contains some coreutils, but the same principle would be in effect)
bonsai/bonuspackwould be fun. Orbonsai/leavesmaybe.im thinking the collection of software should have a straightforward name, but then we can have fun with the tool names. buildutils comes to mind
futzing; utilities that aren't useful except to break things (hell yeah).