!avYyleMexqjFHoqrME:nixos.org

Nix Documentation

405 Members
Discussion about documentation improvements around the Nix ecosystem79 Servers

Load older messages


SenderMessageTime
13 Jul 2021
@jtojnar:matrix.orgJan Tojnarso it would be even more magic (e.g. in github rendering)00:07:02
@jtojnar:matrix.orgJan Tojnarhmm, I guess the xrefs do too00:07:45
@jtojnar:matrix.orgJan Tojnarfinally got the db-to-md conversion script to work – even forces pandoc to use fenced code blocks00:13:27
@jtojnar:matrix.orgJan Tojnar * you did good job, but the API will not allow you do much better00:30:07
@jtojnar:matrix.orgJan Tojnar * you did good job, but the API will not allow you to do much better00:30:15
@jtojnar:matrix.orgJan Tojnar ryantm: one of the reasons I want to do high-fidelity db-to-md is that we still have not decided on the set of features we want to support 00:42:28
@jtojnar:matrix.orgJan Tojnarif we carry over as much as possible, we can then decide we do not want to have manpage links00:43:02
@jtojnar:matrix.orgJan Tojnarbut if we drop them in conversion, it will be PITA to add them back00:43:23
@jtojnar:matrix.orgJan Tojnareventually, I want to make a RFC evaluating each feature individually, based on different criteria00:46:55
@jtojnar:matrix.orgJan Tojnarbut until then, I want to preserve everything that is reasonably simple to preserve00:47:38
@ryantm:matrix.orgryantmSounds good.00:55:03
@jtojnar:matrix.orgJan Tojnar ryantm: I want to recommend the db-to-md script from the PR instead of manual pandoc+prettier invocation 00:58:31
@jtojnar:matrix.orgJan Tojnarnow that we convinced pandoc to use fenced code blocks, we should not even need prettier00:59:34
@ryantm:matrix.orgryantmMaybe we could avoid "footnote" link magic, but aggregating the "footnote" links across the whole set of documents.01:00:16
@ryantm:matrix.orgryantm By "footnote" link, I mean the [link][1] ones 01:00:36
@jtojnar:matrix.orgJan Tojnar so not actual footnotes [link][^1]? 01:01:41
@ryantm:matrix.orgryantmOh, that's a thing in some extension?01:02:33
@jtojnar:matrix.orgJan Tojnar
In reply to @ryantm:matrix.org
Maybe we could avoid "footnote" link magic, but aggregating the "footnote" links across the whole set of documents.
that would be pretty simple by concating the link target definitions to each md file
01:03:06
@jtojnar:matrix.orgJan Tojnarextras would just be ignored01:03:16
@jtojnar:matrix.orgJan Tojnar
In reply to @ryantm:matrix.org
Oh, that's a thing in some extension?
yeah, pandoc supports it
01:03:25
@ryantm:matrix.orgryantm

I just meant the one like this:

[Link][1]
⋮
[1]: http://b.org
01:03:37
@jtojnar:matrix.orgJan Tojnaryou can even use strings instead of numbers01:03:49
@ryantm:matrix.orgryantmRight.01:03:57
@ryantm:matrix.orgryantmSo there could be ones for all the NixOS options, and all the common manpages.01:04:24
@ryantm:matrix.orgryantmThough I guess NixOS options might be xrefs?01:04:48
@jtojnar:matrix.orgJan Tojnaryeah, xref work for options for now 01:05:35
@jtojnar:matrix.orgJan Tojnar I think I still like {manpage}`foo(5)` more compared to something like [][foo(5)], which would still need us to fill in the link text 01:07:53
@jtojnar:matrix.orgJan Tojnarso we would need some way to annotate the anchors that they are manpages01:08:34
@jtojnar:matrix.orgJan Tojnar Or write [`foo(5)`][foo(5)] which is IMO even worse for writers than the MyST role. 01:10:05
@jtojnar:matrix.orgJan Tojnar Something like [](man:foo(5) would bring best of both worlds, I feel, but it is non-standard. 01:12:34

Show newer messages


Back to Room ListRoom Version: 6