| 7 Feb 2025 |
|  sleepymonad left the room. | 08:45:56 |
|  terrorjack left the room. | 22:28:06 |
| 10 Feb 2025 |
|  spacekitteh joined the room. | 03:54:14 |
| 15 Feb 2025 |
|  BenjB83 joined the room. | 10:16:21 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:06 |
| 16 Feb 2025 |
|  KristijanZic joined the room. | 01:04:13 |
| 17 Feb 2025 |
|  Rosuavio joined the room. | 20:07:16 |
|  encode42 joined the room. | 22:18:03 |
| 20 Feb 2025 |
|  John Kha joined the room. | 18:45:04 |
| 24 Feb 2025 |
|  Thunder left the room. | 21:04:39 |
| 27 Feb 2025 |
|  ·☽•Nameless☆•777 · ± changed their profile picture. | 17:13:32 |
| 2 Mar 2025 |
 loudgolem | incase someone wants to answer, https://discourse.nixos.org/t/adding-custom-options-to-nixpkgs-modules-with-arbitrary-attrsets/61039 | 04:12:24 |
 infinisil | loudgolem: Done ) | 04:27:12 |
| infinisil | * loudgolem: Done :) | 04:27:13 |
| 6 Mar 2025 |
 mr-qubo | Is there a mkAfter but for strings? I want to append flags to nixos option programs.captive-browser.browser, and I have no idea how. | 14:40:14 |
 nbp | mkAfter is for any option, so yes, unless you are using dependent strings which are ordered based on dependencies. | 14:42:52 |
 Matt Sturgeon | mkOrder (+ mkBefore & mkAfter) affects the order definitions get merged in, so it is applicable to any mergable type. | 14:42:57 |
| nbp | * mkAfter is for any option, so yes, unless you are using dependent strings which are merged based on dependencies. | 14:43:28 |
| mr-qubo | I've tried using mkAfter and it just replaced the strings enitrely. | 14:43:55 |
| mr-qubo | * I've tried using mkAfter and it just replaced the strings entirely. | 14:44:00 |
| mr-qubo | * I've tried using mkAfter and it just replaced the string entirely. | 14:44:04 |
| nbp | That's because you do not have the same priority level. | 14:44:19 |
| nbp | Or there is a problem with the merge function of the option. | 14:45:37 |
| Matt Sturgeon | Sounds like your definition has a higher override priority. For example a "normal" definition will not be merged with a "default" definition, because merging is only done for definitions of whatever happens to be the highest priority | 14:45:41 |
| mr-qubo | Yes, I want to merge with the default value of that option. | 14:46:34 |
| mr-qubo | This module needs the flags, which are passed in default value. | 14:46:56 |
| nbp | then you need mkDefault (mkAfter suffix) | 14:47:00 |
| Matt Sturgeon | Assuming the option's type actually supports merging, you need to make your definition have the same override priority. This is probably either mkDefault or more likely mkOptionDefault | 14:47:30 |
| nbp | * then you need mkOptionDefault (mkAfter suffix) — editted: wrong function name | 14:48:21 |
| Matt Sturgeon | If the option doesn't support merging, a less idiomatic solution would be to read the option's default value and use that in your overriding definition:
foo = options.foo.default + "suffix";
This is ugly and fragile, but could work as a hacky solution if necessary. | 14:50:45 |
