NixOS Module System | 143 Members | |
| 28 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Jun 2025 | ||
| I see, thanks a lot for the answer! In the end I went with a custom option to store some state about the current eval, which allows me to directly be able to access highestPrio on those options 👍 | 10:11:25 | |
| * I see, thanks a lot for the answer! In the end I went with a custom options to store some state about the current eval, which allows me to directly be able to access highestPrio on those options 👍 | 10:11:35 | |
| Awesome. That sounds more idiomatic! Just a general design titbit: Due to laziness, extended module evals don't actually need to be fully evaluated, so if you only read from the "final" extended configuration, then you don't need to also spend time evaluating the other ones. | 10:18:21 | |
| * I see, thanks a lot for the answer! In the end I'm going with a custom options to store some state about the current eval, which allows me to directly be able to access highestPrio on those options 👍 | 11:39:28 | |
| 23:48:32 | ||
| 2 Jun 2025 | ||
| Yes, I'm quite happy with what I managed to do ✨ I use this in my dotfiles to make mini module systems to configure nvim/zsh/tmux, and incrementally enable various flags for different flake outputs.. | 00:33:01 | |
| * Yes, I'm quite happy with what I managed to do ✨ I use this in my dotfiles to make small independent module systems to configure nvim/zsh/tmux, and incrementally enable various flags for different flake outputs.. | 00:34:14 | |
| 4 Jun 2025 | ||
| 18:30:25 | ||
| 6 Jun 2025 | ||
| 00:18:42 | ||
| 18:45:00 | ||
| 7 Jun 2025 | ||
| 22:32:07 | ||
| 23:25:32 | ||