Nix Documentation | 417 Members | |
| Discussion about documentation improvements around the Nix ecosystem | 87 Servers |
| Sender | Message | Time |
|---|---|---|
| 20 Apr 2024 | ||
In reply to @djacu:matrix.orgThat's pretty much the idea in my sketch, except no hacky insertions into markdown, but rendering markdown from literate programs. | 17:37:58 | |
In reply to @djacu:matrix.org* That's pretty much the idea in my sketch, except no hacky insertions into markdown, but rendering markdown (or anything) from literate programs. | 17:38:10 | |
| Separate files is definitely hacky but worked for me. I had some copy scripts that would build the site and copy the resulting markdown into the live editing area. So I had a pseudo live editing experience. The real big upside to having separate code files is that all the lessons have files that is available to the reader to use right away. Although I wonder if it would be possible to write the code in the markdown, evaluate it (like we are talking about), and also extract it into files so the reader could use them. | 18:22:14 | |
| 21 Apr 2024 | ||
| 06:49:52 | ||
| https://github.com/NixOS/nixpkgs/pull/305767: nixos/manual: abort build on warn | 15:18:24 | |
PR has been updated and takes the existing documentation.nixos.options.warningsAreErrors option into account instead of hard-coding NIX_ABORT_ON_EVAL | 16:21:35 | |
| 16:26:16 | ||
| Hey I noticed a style issue with nix.dev ... the hyperlink color (when not highlighted) is the same color as the blue in-depth explanation expandable backgrounds. | 16:27:36 | |
| Is that the kinda thing I should open an issue about? I am willing to help with it and all | 16:28:21 | |
| (I didn't open an issue, yet, because that seemed like a lot of overhead for such a minor change) | 16:29:26 | |
| 16:57:38 | ||
In reply to @symys:fnord.theinfinitycorporation.comOh neat find, apparently it only happens in the light theme, which is why I haven't seen in before. If you can fix it yourself, a PR would be best! | 20:06:52 | |
In reply to @symys:fnord.theinfinitycorporation.comI can have a look as it's caused by my pr | 20:22:21 | |
| I self merged this time because it would be a major annoyance when one cannot read the tutorial properly. | 21:30:33 | |
In reply to @olafklingt:matrix.orgOh, thanks! Looks good, much easier to read and still in color scheme. | 22:55:51 | |
| 22 Apr 2024 | ||
| fricklerhandwerk: this commit https://github.com/NixOS/nix.dev/pull/940/commits/b556495361e12a9e81adc8080e362ea032b1e123 reverts the change i made to find a middle ground between having the command in the text and removing it. is this on purpose? | 16:46:40 | |
| The NixOS admonition and the footnote were essentially the same thing, and the footnote requires jumping around. Or did we miss something? I’ll fix up the breakage of course | 16:50:03 | |
In reply to @fricklerhandwerk:matrix.orgthe jumping implied by a footnote highlights that its not part of the flow of argument. but keeping the reference helps to move between parts of the documentation. | 16:53:20 | |
| Python Docs PR: https://github.com/NixOS/nixpkgs/pull/306119 | 22:29:07 | |
| 23 Apr 2024 | ||
| 16:48:19 | ||
| 24 Apr 2024 | ||
| 08:59:13 | ||
| 17:37:04 | ||
| I'm going through the packaging tutorial at https://nix.dev/tutorials/packaging-existing-software.html and evaluating the example skeleton derivation gives a
| 19:10:05 | |
| stablejoy: Nice catch! Would you mind PRing that quick fix? | 19:18:40 | |
In reply to @infinisil:matrix.orgYes Id love to thanks! | 19:21:06 | |
| Sorry guys was a bit busy last two weeks trying to shave some time off tomorrow for fixing nixdoc (again 😀). | 21:28:13 | |
| Johannes Kirschbauer @hsjobeki: No worries ;) | 22:37:52 | |
| aw I did the PR, it's my first ever, it's waiting to be merged. I cried. | 22:47:54 | |
| stablejoy: Ah nice, didn't see it because it has a dedicated code owner that gets pinged (which overrides the default code owner of the entire team). Thanks, merging! | 22:56:56 | |
| 25 Apr 2024 | ||
| I won't make the meeting today. infinisil will you be in? | 07:37:32 | |