doc: explicit Markdown anchors for top-level headings; remove metadata

I used the existing anchors generated by Docbook, so the anchor part
should be a no-op. This could be useful depending on the
infrastructure we choose to use, and it is better to be explicit than
rely on Docbook's id generating algorithms.

I got rid of the metadata segments of the Markdown files, because they
are outdated, inaccurate, and could make people less willing to change
them without speaking with the author.
wip/yesman
Ryan Mulligan 3 years ago
parent 70a061bd6c
commit b8344f9e5c
  1. 2
      doc/builders/packages/cataclysm-dda.section.md
  2. 2
      doc/builders/trivial-builders.chapter.md
  3. 7
      doc/languages-frameworks/agda.section.md
  4. 7
      doc/languages-frameworks/android.section.md
  5. 2
      doc/languages-frameworks/crystal.section.md
  6. 2
      doc/languages-frameworks/emscripten.section.md
  7. 8
      doc/languages-frameworks/haskell.section.md
  8. 2
      doc/languages-frameworks/idris.section.md
  9. 7
      doc/languages-frameworks/ios.section.md
  10. 8
      doc/languages-frameworks/lua.section.md
  11. 8
      doc/languages-frameworks/maven.section.md
  12. 4
      doc/languages-frameworks/node.section.md
  13. 2
      doc/languages-frameworks/python.section.md
  14. 3
      doc/languages-frameworks/r.section.md
  15. 8
      doc/languages-frameworks/rust.section.md
  16. 1
      doc/languages-frameworks/texlive.section.md
  17. 7
      doc/languages-frameworks/titanium.section.md
  18. 7
      doc/languages-frameworks/vim.section.md
  19. 8
      doc/preface.chapter.md

@ -1,4 +1,4 @@
# Cataclysm: Dark Days Ahead
# Cataclysm: Dark Days Ahead {#cataclysm-dark-days-ahead}
## How to install Cataclysm DDA

@ -37,7 +37,7 @@ This works just like `runCommand`. The only difference is that it also provides
Variant of `runCommand` that forces the derivation to be built locally, it is not substituted. This is intended for very cheap commands (<1s execution time). It saves on the network roundrip and can speed up a build.
::: {.note}
::: note
This sets [`allowSubstitutes` to `false`](https://nixos.org/nix/manual/#adv-attr-allowSubstitutes), so only use `runCommandLocal` if you are certain the user will always have a builder for the `system` of the derivation. This should be true for most trivial use cases (e.g. just copying some files to a different location or adding symlinks), because there the `system` is usually the same as `builtins.currentSystem`.
:::

@ -1,9 +1,4 @@
---
title: Agda
author: Alex Rice (alexarice)
date: 2020-01-06
---
# Agda
# Agda {#agda}
## How to use Agda

@ -1,9 +1,4 @@
---
title: Android
author: Sander van der Burg
date: 2018-11-18
---
# Android
# Android {#android}
The Android build environment provides three major features and a number of
supporting features.

@ -1,4 +1,4 @@
# Crystal
# Crystal {#crystal}
## Building a Crystal package

@ -1,4 +1,4 @@
# Emscripten
# Emscripten {#emscripten}
[Emscripten](https://github.com/kripken/emscripten): An LLVM-to-JavaScript Compiler

@ -1,10 +1,4 @@
---
title: User's Guide for Haskell in Nixpkgs
author: Peter Simons
date: 2015-06-01
---
# Haskell
# Haskell {#haskell}
The documentation for the Haskell infrastructure is published at
<https://haskell4nix.readthedocs.io/>. The source code for that

@ -1,4 +1,4 @@
# Idris
# Idris {#idris}
## Installing Idris

@ -1,9 +1,4 @@
---
title: iOS
author: Sander van der Burg
date: 2019-11-10
---
# iOS
# iOS {#ios}
This component is basically a wrapper/workaround that makes it possible to
expose an Xcode installation as a Nix package by means of symlinking to the

@ -1,10 +1,4 @@
---
title: Lua
author: Matthieu Coudron
date: 2019-02-05
---
# User's Guide to Lua Infrastructure
# User's Guide to Lua Infrastructure {#users-guide-to-lua-infrastructure}
## Using Lua

@ -1,10 +1,4 @@
---
title: Maven
author: Farid Zakaria
date: 2020-10-15
---
# Maven
# Maven {#maven}
Maven is a well-known build tool for the Java ecosystem however it has some challenges when integrating into the Nix build system.

@ -1,5 +1,5 @@
Node.js
=======
# Node.js {#node.js}
The `pkgs/development/node-packages` folder contains a generated collection of
[NPM packages](https://npmjs.com/) that can be installed with the Nix package
manager.

@ -1,4 +1,4 @@
# Python
# Python {#python}
## User Guide

@ -1,5 +1,4 @@
R
=
# R {#r}
## Installation

@ -1,10 +1,4 @@
---
title: Rust
author: Matthias Beyer
date: 2017-03-05
---
# Rust
# Rust {#rust}
To install the rust compiler and cargo put

@ -1,4 +1,3 @@
# TeX Live {#sec-language-texlive}
Since release 15.09 there is a new TeX Live packaging that lives entirely under attribute `texlive`.

@ -1,9 +1,4 @@
---
title: Titanium
author: Sander van der Burg
date: 2018-11-18
---
# Titanium
# Titanium {#titanium}
The Nixpkgs repository contains facilities to deploy a variety of versions of
the [Titanium SDK](https://www.appcelerator.com) versions, a cross-platform

@ -1,9 +1,4 @@
---
title: User's Guide for Vim in Nixpkgs
author: Marc Weber
date: 2016-06-25
---
# Vim
# Vim {#vim}
Both Neovim and Vim can be configured to include your favorite plugins
and additional libraries.

@ -1,10 +1,4 @@
---
title: Preface
author: Frederik Rietdijk
date: 2015-11-25
---
# Preface
# Preface {#preface}
The Nix Packages collection (Nixpkgs) is a set of thousands of packages for the
[Nix package manager](https://nixos.org/nix/), released under a

Loading…
Cancel
Save