| 5 Dec 2025 |
 maralorn | Problem is I really need an internal-json log of an offending build to figure this out. | 10:19:09 |
 Emma [it/its] | hmm, if you can hack in support for passing a wrapper command (with maybe an arg or 2) i could probably bridge the nix logs as requested by nom to a matrix room | 10:21:17 |
| Emma [it/its] | or store them in a file somewhere... | 10:21:55 |
| Emma [it/its] | with the former i'd expect you to be able to tail my logs in ~realtime, give or take federation lag | 10:26:00 |
| Emma [it/its] | i dont expect this to finish in the next couple of hours soo... ill go fix up some packaging woes and see if i can build a simple matrix bridge for logs | 10:37:54 |
 saygo.2 | i think you can just use tee to split the stdout/stderr streams | 10:41:24 |
| saygo.2 | just use plain nom with a pipe and tee | 10:41:40 |
| saygo.2 | not enough of a shell wizard to give you the exact commands but it should be possible | 10:42:18 |
