| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This matches the terminology in Eelco's thesis.
|
|
Co-authored-by: Matthieu Coudron <teto@users.noreply.github.com>
|
|
Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de>
|
|
Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de>
|
|
Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de>
|
|
|
|
|
|
They are too advanced for up front.
|
|
|
|
|
|
|
|
The current docs are all "how to do things" and no "what is Nix" or "why
are things the way they are".
I see lots of misconception on the wider internet, and I also think we
would benefit from a "living document" to answer some questions people
currently turn to the thesis for.
I think a new section of the manual can address all these issues.
|
|
manual: use subheadings for primitive types
|
|
|
|
to make it consistent with builtins and configuration options
|
|
`nix ping-store` -> `nix store ping`.
|
|
Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com>
|
|
|
|
|
|
"simple" is a loaded term
|
|
this gives us HTML anchors for each of them
|
|
reword description to have shorter sentences.
|
|
|
|
|
|
Fix logical and typographical errors in nix-env man page
|
|
|
|
|
|
cc @gytis-ivaskevicius
|
|
|
|
Co-authored-by: Théophane Hufschmitt <7226587+thufschmitt@users.noreply.github.com>
|
|
This should help future lost newcomers like myself understand where to
find the docs for both of these commands and how they differ.
|
|
|
|
|
|
|
|
|
|
E.g. 'nix build nixpkgs#libxml2.dev' will build the 'dev' output.
|
|
|
|
There are still many links to the old manual on the web and
having them end up on the Introduction page is a bad user experience.
|
|
|
|
Added using the following sed scripts:
- For command-ref/opt-common.md:
s~- `(--?)([^`]+)`~- [`\1\2`]{#opt-\2}~g
- For expressions/builtin-constants.md:
s~- `(builtins\.?)([^`]+)`~- [`\1\2`]{#builtins-\2}~g
- For expressions/advanced-attributes.md
s~^ - `([^`]+)`~ - [`\1`]{#adv-attr-\1}~g
and manually adjusted outputHashAlgo & outputHashMode.
- For glossary.md
s~^ - (`([^`]+)`|(.+)) ?\\~ - [\1]{#gloss-\2\3}\\~g;
s~(gloss-\w+) ~\1-~g
and manually adjusted anchors for Nix expression, user environment, NAR, ∅ and ε.
- For command-ref/env-common.md
s~^ - `([^`]+)`~ - [`\1`]{#env-\1}~g'
|
|
Python is only pulled into the build closure by Mercurial, which might end up being removed.
Let’s port the script to jq, which is more likely to stay.
|
|
It is now possible to use the following syntax to insert anchors into the text:
[]{#anchor-name}
The anchor will allow linking to the location it is placed by appending #anchor-name to the URL.
Additionally, it is possible to create a link pointing to its own location by adding text between the square brackets:
[`--add-root`]{#opt-add-root}
|
|
|
|
|
|
|
|
|
|
|
|
Add a new `file` fetcher type, which will fetch a plain file over
http(s), or from the local file.
Because plain `http(s)://` or `file://` urls can already correspond to
`tarball` inputs (if the path ends-up with a know archive extension),
the URL parsing logic is a bit convuluted in that:
- {http,https,file}:// urls will be interpreted as either a tarball or a
file input, depending on the extensions of the path part (so
`https://foo.com/bar` will be a `file` input and
`https://foo.com/bar.tar.gz` as a `tarball` input)
- `file+{something}://` urls will be interpreted as `file` urls (with
the `file+` part removed)
- `tarball+{something}://` urls will be interpreted as `tarball` urls (with
the `tarball+` part removed)
Fix #3785
Co-Authored-By: Tony Olagbaiye <me@fron.io>
|
