Nix Documentation | 427 Members | |
| Discussion about documentation improvements around the Nix ecosystem | 88 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 Mar 2024 | ||
| Those cases (and what we're doing with them) aren't documented right now, and the way we handle these will likely change in the future, which is why we're being a bit conservative with the move | 17:23:02 | |
oh wow we only now get to see the backlog. someone asked about multipage rendering in nrd it seems? html:into-file makes that happen, the manual already uses that to render the option docs and appendix. isn't automated per chapter/part, but could be added easily (the infra to do this is there already) | 18:13:51 | |
getting the official manual to render multipage is literally just sprinkling html:into-file directives on the includes and letting it build | 18:14:46 | |
| (which, we do want to stress at the risk of offending someone, we have said at least five different times, including in meetings of the docs team) | 18:15:58 | |
| (Without also offending) Was it a lack of contributions? or why don't we have a multi-page outut if it's trivial and has been said so many times? It would be interesting to know whats the root cause then. | 18:56:19 | |
| lack of contributions probably. the topic has come up often enough and we replied how often enough but were burned out enough to not do the splitting work | 18:57:00 | |
| might've also just been forgetten time and time again. | 18:57:52 | |
| I'll definitely look into it. | 18:58:52 | |
| in any case it would be easy to split the manual as is, and with just a little work the split could be done programmatically based on toc structure too. that's part of why the toc data structures are the way they are | 18:59:12 | |
| (we haven't read much of the backlog past seeing that the question must've existed because that part was full of build logs, and the backlog didn't go much further anyway. gotta love matrix) | 19:00:38 | |
| Do you have the issue number? can't find it on the project board. | 19:02:29 | |
| issue number for what? | 19:02:54 | |
| I assumed we had an issue for page splitting. Might not be true then? | 20:52:54 | |
| ah. can't remember one immediately at least | 20:53:50 | |
| yeah, there isn't one we could find either | 20:57:09 | |
| There's some top-level attribute Ideas? | 21:53:40 | |
| * There's some top-level attribute Ideas? | 21:53:58 | |
| set by the flake machinery because it's a git repo, probably | 21:54:42 | |
In reply to @pennae:matrix.eno.space Hm no, at least I don't see how a flake would do that. An empty flake like this:
called with | 21:59:30 | |
In reply to @pennae:matrix.eno.space* Hm no, at least I don't see how a flake would do that. An empty flake in a Git repo, like this:
called with | 21:59:58 | |
| commit it | 22:03:24 | |
| I did | 22:03:31 | |
| shows up having a rev for us | 22:03:47 | |
| Ah okay, apparently something was weird when using an existing repo. It worked in a clean one. | 22:04:23 | |
| Thanks. Cursed stuff. | 22:06:21 | |
| that's flakes for you | 22:06:28 | |
https://www.catb.org/esr/writings/unix-koans/ten-thousand.html | 22:08:32 | |
| 17 Mar 2024 | ||
In reply to @fricklerhandwerk:matrix.orgindeed, the wiki is useful but I also find it goes into too much detail with flag setting. most of the time, if you set up things correctly, it should "just work". maybe I can add a section here in the meantime | 01:00:37 | |
In reply to @fricklerhandwerk:matrix.orgthat is good to see! I was actually thinking about the writers that live under scripts.nix (confusingly named indeed). these let you write python and many other languages inline and are, afaict not in the manual at all | 01:02:20 | |
| there is an aged issue about it: https://github.com/NixOS/nixpkgs/issues/89759 | 01:03:11 | |