From 13befa5263645d69e71323f0c9d2609d9d1f176a Mon Sep 17 00:00:00 2001 From: Jan Klass Date: Wed, 16 Jul 2025 19:47:56 +0200 Subject: [PATCH] Add missing example output Reduce items to evade excessive output. --- lang-guide/chapters/types/basic_types/closure.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/lang-guide/chapters/types/basic_types/closure.md b/lang-guide/chapters/types/basic_types/closure.md index 6638e46e0f9..e25efa25c9d 100644 --- a/lang-guide/chapters/types/basic_types/closure.md +++ b/lang-guide/chapters/types/basic_types/closure.md @@ -71,7 +71,15 @@ Closures are used in Nu extensively as parameters to iteration style commands li 1. You can also use [pipeline input as `$in`](pipelines.html#pipeline-input-and-the-special-in-variable) in most closures instead of providing an explicit parameter. For example: ```nu - 1..10 | each { print $in } + 1..5 | each { print $in } + # => 1 + # => 2 + # => 3 + # => 4 + # => 5 + # => ╭────────────╮ + # => │ empty list │ + # => ╰────────────╯ ``` 1. You can also pass closures themselves into a pipeline assuming the next command knows how to consume it. For example, the `do` example can be rewritten as: