aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/rl-next/better-errors-in-nix-repl.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual/rl-next/better-errors-in-nix-repl.md')
-rw-r--r--doc/manual/rl-next/better-errors-in-nix-repl.md42
1 files changed, 0 insertions, 42 deletions
diff --git a/doc/manual/rl-next/better-errors-in-nix-repl.md b/doc/manual/rl-next/better-errors-in-nix-repl.md
deleted file mode 100644
index 2f2714a0e..000000000
--- a/doc/manual/rl-next/better-errors-in-nix-repl.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-synopsis: Concise error printing in `nix repl`
-prs: 9928
-cls: 811
-category: Improvements
-credits: 9999years
----
-
-Previously, if an element of a list or attribute set threw an error while
-evaluating, `nix repl` would print the entire error (including source location
-information) inline. This output was clumsy and difficult to parse:
-
-```
-nix-repl> { err = builtins.throw "uh oh!"; }
-{ err = «error:
- … while calling the 'throw' builtin
- at «string»:1:9:
- 1| { err = builtins.throw "uh oh!"; }
- | ^
-
- error: uh oh!»; }
-```
-
-Now, only the error message is displayed, making the output much more readable.
-```
-nix-repl> { err = builtins.throw "uh oh!"; }
-{ err = «error: uh oh!»; }
-```
-
-However, if the whole expression being evaluated throws an error, source
-locations and (if applicable) a stack trace are printed, just like you'd expect:
-
-```
-nix-repl> builtins.throw "uh oh!"
-error:
- … while calling the 'throw' builtin
- at «string»:1:1:
- 1| builtins.throw "uh oh!"
- | ^
-
- error: uh oh!
-```