NixOS Module System | 142 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 | ||
| 9 Jun 2025 | ||
| 13:06:30 | ||
| 20:46:30 | ||
| 16 Jun 2025 | ||
| Redacted or Malformed Event | 07:00:33 | |
| 21:50:42 | ||
| 17 Jun 2025 | ||
| 12:06:51 | ||
| 22 Jun 2025 | ||
| 12:14:58 | ||
| 23 Jun 2025 | ||
| 15:36:50 | ||
| 27 Jun 2025 | ||
| 17:25:55 | ||
| 30 Jun 2025 | ||
| 03:04:43 | ||
| 2 Jul 2025 | ||
| 13:30:44 | ||
| 4 Jul 2025 | ||
| 21:28:45 | ||
| 7 Jul 2025 | ||
| 13:12:04 | ||
| 8 Jul 2025 | ||
| 09:11:18 | ||
| Hey guys, I am trying to modularize my system, but there's one thing that I can't grasp. When you see everyone using Nix modules to split their configs, they almost always have their home manager configuration separate from their system configuration. I mean, it makes sense 95% of time, however, for some programs, like for example Hyprland, if you want to use Home Manager to manage Hyprland, you need the system module enabled as well. Basically everyone I've seen simply has a hyprland.nix config file both in the home-manager config as well as the system config. However, this means they're decoupled. If I am choosing which modules to enable inside my host, I have to think about enabling both my user hyprland module as well as my system hyprland module (which are in different parts of my dotfiles, since one of them is inside the home-manager configuration directory and the other one is inside the system configuration directory). How do I properly manage this sort of thing? | 09:17:03 | |