| 21 Jul 2025 |
 nbp | x10an14: This is the right channel. Thanks for the link, I was not aware of the pipe operator. | 12:03:29 |
 x10an14 | Aight, and yw =) | 12:07:17 |
| 25 Jul 2025 |
|  hsjobeki joined the room. | 12:11:00 |
| 31 Jul 2025 |
|  unwary joined the room. | 00:25:28 |
| unwary | This might be the wrong chat, but I'm trying to understand how to package something like a .desktop file so that a module I write will be included in start menus and such. Right now, enabling my module gets me the executable available on the command line, but as it's a GUI program, that's suboptimal. | 00:26:59 |
 @mightyiam:matrix.org | There's plenty of examples in Nixpkgs. Did you find some? | 06:42:08 |
| @mightyiam:matrix.org | And yes, this isn't quite the correct room. | 06:42:25 |
|  sammy (It/Its) joined the room. | 09:35:10 |
|  Sammy (It/Its) left the room. | 10:02:52 |
| unwary | I did not, or did not detect it. I seemed to examine modules that used various build-wrapping tools that I presumed handled that as part of the build. | 23:53:39 |
| 1 Aug 2025 |
| @mightyiam:matrix.org | Sorry for not being clear. It's not in a NixOS module typically, but in the package for some piece of software. And might not be obvious. The part of this that is in the NixOS module is that the package of the software ends up in environment.systemPackages and includes the .desktop file. | 06:32:42 |
|  yan 💕 joined the room. | 15:42:19 |
| 5 Aug 2025 |
|  isabel changed their profile picture. | 09:49:13 |
|  Axel Karjalainen joined the room. | 18:48:14 |
| 6 Aug 2025 |
|  vidariondr set a profile picture. | 18:31:00 |
| 7 Aug 2025 |
| @mightyiam:matrix.org | https://discourse.nixos.org/t/nixpkgs-module-system-config-modules-graph/67722?u=mightyiam | 16:53:44 |
| nbp | Let's see how much time it take before someone ask what is the difference between key and file. | 17:05:23 |
| nbp | Now people might understand why you should not write a NixOS module within a flake, because it lacks position information.
{agenix, ...}:
{
# Using the module directly prevent the deduplication from working properly.
imports = [
agenix.nixosModules.default
];
}
| 17:11:50 |
| nbp | * Now people might understand why you should not write a NixOS module within a flake.nix file, because it lacks position information.
{agenix, ...}:
{
# Using the module directly prevent the deduplication from working properly.
imports = [
agenix.nixosModules.default
];
}
| 17:12:41 |
| 8 Aug 2025 |
|  0x4A6F joined the room. | 06:31:30 |
| nbp | (oh, this has been fixed a year ago in agenix) | 12:33:22 |
 ibizaman | I have an option whose type is optionType. So in the config part, I define what the type actually is. Is it possible for this "instantiated" option to appear in the documentation/the manual? | 21:34:48 |
| ibizaman | Right now I see the description for the optionType but not for the "instantiated" option. | 21:35:45 |
| hsjobeki | I would say no. Documentation is only generated from options. Since the actual type is defined in config.
But i guess the values is then mapped into some module as option. There you could get the docs | 23:02:08 |
| ibizaman | Makes sense indeed. Thanks! | 23:19:42 |
| 9 Aug 2025 |
|  seapat set a profile picture. | 14:23:12 |
| 11 Aug 2025 |
|  Spaenny changed their display name from Philipp to Spaenny. | 14:47:13 |
| 18 Aug 2025 |
|  redblueflame set a profile picture. | 14:25:54 |
| redblueflame changed their display name from redblueflame to knownasred. | 14:26:00 |
| 20 Aug 2025 |
|  jopejoe1 changed their display name from jopejoe1 (4094@GPN23) to jopejoe1. | 18:50:36 |
