| 27 Mar 2026 |
|  smoothie_one joined the room. | 13:07:26 |
|  @mhia09:keimai.space left the room. | 21:14:15 |
|  Sapii joined the room. | 22:49:07 |
| 30 Mar 2026 |
|  RITISH DAS joined the room. | 17:14:08 |
| 1 Apr 2026 |
|  Tuxfanou joined the room. | 19:22:43 |
| 10 Apr 2026 |
|  ebeem-sama changed their profile picture. | 13:57:50 |
| 12 Apr 2026 |
|  @lucailgarb:matrix.org joined the room. | 08:59:57 |
| 13 Apr 2026 |
|  TikTorchic18 joined the room. | 01:12:20 |
|  Alesya changed their display name from Alesya Huzik to Alesya. | 01:48:08 |
|  Adrien changed their display name from Adrien to Dadou. | 19:56:41 |
| Adrien changed their display name from Dadou to Adrien. | 19:57:11 |
| 15 Apr 2026 |
|  whispers [& it/fae] joined the room. | 01:30:47 |
| 17 Apr 2026 |
|  dish [Fox/It/She] changed their profile picture. | 16:58:37 |
| 18 Apr 2026 |
|  @rasmata:matrix.org joined the room. | 14:39:38 |
| @rasmata:matrix.org left the room. | 14:39:42 |
| 19 Apr 2026 |
|  Lukas joined the room. | 02:20:20 |
| 20 Apr 2026 |
| @lucailgarb:matrix.org left the room. | 09:18:25 |
| 27 Apr 2026 |
|  Ninja joined the room. | 14:32:11 |
| 30 Apr 2026 |
|  isabel changed their profile picture. | 18:47:13 |
| 3 May 2026 |
| isabel changed their profile picture. | 10:38:53 |
| 5 May 2026 |
|  @gdesforges:matrix.org left the room. | 10:45:12 |
| 8 May 2026 |
 ibizaman | Hello all, I was wondering if there was some work on making nix documentation executable? In my project I extensively use nmd to build the documentation but what I see missing is that I can’t test the examples and snippets I’m writing and they inevitably become stale. | 15:26:48 |
| ibizaman | * Hello all, I was wondering if there was some work on making nix documentation executable? In my project I extensively use nmd to build the documentation but what I see missing is that I can’t test the examples and snippets I’m writing and they inevitably become stale. I did some light research on this but didn’t find anything. | 15:27:12 |
| ibizaman | FWIW I looked at existing literate programming tools but they are all so verbose. And they somehow don’t support markdown files for the major part. I thought I’d just roll my own parser using some markdown lib to just concatenate all source code but I’d like for others to be able to use it instead of this sitting in my own repo. | 16:06:07 |
| 11 May 2026 |
 Christian Friedow | The only thing that comes to my mind is https://ngi.nixos.org/. They provide executable examples that spin up VMs. But I guess what you are talking about is more like small code snippets that you can execute in a browser.
What project are you working on? And where are you rendering documentation to (man pages, documentation website, help flags in cli tools or code)? | 07:29:29 |
 fricklerhandwerk | In reply to @ibizaman:matrix.org
Hello all, I was wondering if there was some work on making nix documentation executable? In my project I extensively use nmd to build the documentation but what I see missing is that I can’t test the examples and snippets I’m writing and they inevitably become stale. I did some light research on this but didn’t find anything. The most generic — and indeed language-agnostic — tool for this is noweb. It’s extremely simple and thanks to Nix-based workflows, easy to control. There’s also modern variants that convert the block annotations to something other than TeX, and the mechanism is so simple one can implement any custom format on a whim. | 09:42:58 |
 figsoda | u might also be able to run some nix implementation in wasm like snix | 17:09:43 |
 hsjobeki | unified js let's you build whatever you want for markdown.
If it's a web page it uses JavaScript anyways.
Remark, rehype plugins are the both tools that I would use to build this myself. Noweb has some benefits but it seems pretty niche. Unified.js is the defacto standard in frontend for processing markdown. (Afaik)
If it's just for evaluation you can call snix as mentioned via wasm directly in the browser. | 17:20:21 |
| hsjobeki | * unified js let's you build whatever you want for markdown.
If it's a web page it uses JavaScript anyways.
Remark, rehype plugins are the both tools that I would use to build this myself. Noweb has some benefits but it seems pretty niche. Unified.js is the defacto standard in frontend for processing markdown. (Afaik)
For evaluation you can call snix as mentioned via wasm directly in the browser. For more than that you might need a backend | 17:21:16 |
| hsjobeki | Or is it a local cli thingy | 17:23:51 |
