| 30 Jun 2023 |
| ruby changed their profile picture. | 14:02:47 |
Sandro 🐧 | FYI https://github.com/NixOS/nixpkgs/pull/240754 | 16:15:47 |
sterni | pennae: maybe every md file for the manual could have an unique prefix assigned to it (e.g. haskell- for haskell.section.md). The md toolchain would then prefix every reference in the markdown file with that unless it is already prefixed. That would ensure unique anchors as long as the prefixes are unique.
Problem is of course that anchors would be changed, maybe we'd need to generously whitelist existing ones.
| 16:16:14 |
sterni | * pennae: maybe every md file for the manual could have an unique prefix assigned to it (e.g. haskell- for haskell.section.md). The md toolchain would then prefix every reference in the markdown file with that unless it is already prefixed. That would ensure unique anchors as long as the prefixes are unique.
Problem is of course that anchors would be changed, maybe we'd need to generously whitelist existing ones. Still seems better than uuids.
Personally I'd also just be fine with a linter that checks for link uniqueness
| 16:16:37 |
pennae | that's an option too, though we'd have to include the path of the file from the doc root instead of just the file name itself (and that can get pretty long) | 16:42:55 |
pennae | nrd already checks for uniqueness and throws an error on duplicates, but that's a pretty bad experience. and the anchors that are likely to be problematic are exactly the ones that don't convey meaning | 16:43:37 |
sterni | pennae: just have a list | 16:55:11 |
sterni | well then just have meaningful anchors :) | 16:55:47 |
pennae | In reply to @sternenseemann:systemli.org well then just have meaningful anchors :) tell docs authors that D: | 16:58:10 |
pennae | like. te python chapter has a section with the id faq | 16:58:52 |
pennae | * like. the python chapter has a section with the id faq | 16:59:05 |