aboutsummaryrefslogtreecommitdiff
path: root/doc/manual
diff options
context:
space:
mode:
authoreldritch horrors <pennae@lix.systems>2024-03-08 04:08:08 +0100
committereldritch horrors <pennae@lix.systems>2024-03-09 04:04:46 +0100
commit7e1f8b09a4968447ec039f2369919fcb2bd430b7 (patch)
tree768f4ef69d4b416ff8c1a64751e1b009aa0c2db2 /doc/manual
parent512c1f05c37c612347dd1fda4771a09744a1a3cd (diff)
Merge pull request #9755 from 9999years/printer-followup
Printer followup (cherry picked from commit 51f524c629b778b75cb62a9e0c85bae655984abc) Change-Id: I29214cc86c5e846cbcfec382022293a70011b316
Diffstat (limited to 'doc/manual')
-rw-r--r--doc/manual/src/command-ref/nix-instantiate.md12
1 files changed, 4 insertions, 8 deletions
diff --git a/doc/manual/src/command-ref/nix-instantiate.md b/doc/manual/src/command-ref/nix-instantiate.md
index 483150aa8..479c9abcf 100644
--- a/doc/manual/src/command-ref/nix-instantiate.md
+++ b/doc/manual/src/command-ref/nix-instantiate.md
@@ -44,9 +44,10 @@ standard input.
> **Warning**
>
- > This option produces ambiguous output which is not suitable for machine
- > consumption. For example, these two Nix expressions print the same result
- > despite having different types:
+ > This option produces output which can be parsed as a Nix expression which
+ > will produce a different result than the input expression when evaluated.
+ > For example, these two Nix expressions print the same result despite
+ > having different meaning:
>
> ```console
> $ nix-instantiate --eval --expr '{ a = {}; }'
@@ -179,12 +180,7 @@ $ nix-instantiate --eval --xml --expr '{ x = {}; }'
</attr>
</attrs>
</expr>
-```
-
-Note that `y` is left unevaluated (the XML representation doesn’t
-attempt to show non-normal forms).
-```console
$ nix-instantiate --eval --xml --strict --expr '{ x = {}; }'
<?xml version='1.0' encoding='utf-8'?>
<expr>