| 23 Feb 2024 |
 maralorn | * A fix would be trivial, but I never dared to approach that because it requires adding nom specific plumbing directly in the nixpkgs code. Although at this point I think nom has so much traction in the community that opt-in nom support in nixos-rebuild would probably be accepted. | 16:27:25 |
 Philip Taron (UTC-8) | It looks like there's just one place that nix-build is called in nixos-rebuild. I'll see if I can substitute it in my own overlay. | 16:28:22 |
| Philip Taron (UTC-8) | (Thank you for nom, btw. Beautiful piece of work.) | 16:29:26 |
| maralorn | Philip Taron (UTC-8): If you find that a specific change in nom would be helpful, please let me know. | 16:29:46 |
 K900 | I'm pretty sure it should be very easy to add | 16:30:12 |
| maralorn | Also if you find some solution which could reasonably be upstreamed into nixpkgs, that would be awesome. | 16:30:14 |
| maralorn | K900 ⚡️: I also think so. | 16:30:35 |
| K900 | I've read nixos-rebuild like two days ago | 16:31:07 |
| 25 Feb 2024 |
|  @qbit:tapenet.org joined the room. | 20:14:06 |
| @qbit:tapenet.org | hi! | 20:14:34 |
| @qbit:tapenet.org | is there a way to completely disable color output? | 20:14:44 |
| maralorn | qbit: Currently not, now. | 21:57:23 |
| maralorn | Why would you want that? | 21:57:33 |
| maralorn | incidentally: Even if I disable the colors in nom the nix build log could still contain colors. | 21:58:00 |
| maralorn | You can open a feature request issue on github. | 21:58:52 |
| maralorn | Currently nom is not very configurable, but once it is a flag like that would be easy to add. | 21:59:16 |
