| 17 Nov 2025 |
 maralorn | e.g. --nom-show-tree | 15:29:08 |
| maralorn | Or --nom-show-outputs | 15:29:35 |
 saygo.2 | In reply to @maralorn:maralorn.de
I haven’t made up my mind about this. There are different thinks to consider, e.g. how to not break tab completion. Ill see how optparse applicative handles this. There is some support for wrapper programs like nom for example here https://hackage-content.haskell.org/package/optparse-applicative-0.19.0.0/docs/Options-Applicative.html#v:forwardOptions and completions should be customizable enough to make -- work well too | 15:38:22 |
| maralorn | Cool! | 15:38:55 |
| maralorn | This is relatively greenfield so if you find arguments to do stuff differently please tell me so that we can discuss. | 15:39:35 |
| saygo.2 | i've just moved and dont have internet yet except mobile data so work is slow on this lol | 15:39:34 |
| maralorn | 😄 | 15:40:42 |
| saygo.2 | You are having fun with this codebase, that required type arguments extension just came out! | 19:45:37 |
| maralorn | Totally. nom is my playground. 😄 | 19:54:35 |
 hexa | 
Download image.png | 21:44:31 |
| hexa | 5334.? | 21:44:39 |
| hexa | 
Download image.png | 21:46:35 |
| hexa | craaaazy numbers | 21:46:36 |
| maralorn | Oooookay | 21:50:54 |
| maralorn | Whatever. | 21:50:57 |
| maralorn | I’ll remove the progress for builds again. | 21:51:17 |
| hexa | hdcd: hexa@build1.darmstadt.ccc.de
hcdd: hexa@build2.darmstadt.ccc.de
🤔 | 21:54:08 |
| hexa | * hdcd: hexa@build1.darmstadt.ccc.de
hccd: hexa@build2.darmstadt.ccc.de
🤔 | 21:54:12 |
| hexa | * hdcd: hexa@build1.darmstadt.ccc.de
hdcd: hexa@build2.darmstadt.ccc.de
🤔 | 21:54:15 |
| maralorn | Yeah, I know. I plan to write a smart disambiguation there. | 21:56:46 |
| maralorn | i.e. I would probably wan’t this to be b1dcd and b2dcd | 21:57:08 |
| hexa | or bdcdN | 21:58:25 |
| hexa | * or bdcd1 | 21:58:27 |
| hexa | don't parse the number in the hostname, just enumerate them | 21:58:44 |
| maralorn | Huh, that would be easier, true. | 21:59:07 |
| 18 Nov 2025 |
| hexa | there are builds that log a percentage progress | 00:48:59 |
| hexa | e.g. cmake builds go [ 23%] foobar [100%] every few lines | 00:49:24 |
| hexa | * e.g. cmake builds go [ 23%] foobar [100%] foobar every few lines | 00:49:31 |
| hexa | that would be a worthwhile thing to display, I think | 00:49:44 |
| hexa | or bazel | 00:49:51 |
