From bd941bfb7f479d4a35f6be040702b714982a553a Mon Sep 17 00:00:00 2001
From: Kaz Kylheku <kaz@kylheku.com>
Date: Mon, 23 May 2016 16:01:41 -0700
Subject: Neglected documentation about @(next).

txr.1: It wasn't documented that expr in @(next expr)
can produce a stream.
---
 txr.1 | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/txr.1 b/txr.1
index a33d036a..89f8d115 100644
--- a/txr.1
+++ b/txr.1
@@ -3200,9 +3200,9 @@ to \*(TX on the command line.
 
 If
 .meta source
-is given, it must be string-valued Lisp expression which denotes an
-input source; it may be a string literal, quasiliteral or a string-valued
-variable.  For instance, if variable
+is given, it must be a \*(TL expression which denotes an
+input source. Its value may be a string or an input stream.
+For instance, if variable
 .code A
 contains the text
 .strn "data" ,
@@ -3214,6 +3214,11 @@ and
 .code "@(next `@A.txt`)"
 means to switch to the file
 .strn "data.txt" .
+The directive
+.code "@(next (open-command `git log`))"
+switches to the input stream connected to the output of the
+.code "git log"
+command.
 
 If the input source cannot be opened for whatever reason,
 \*(TX throws an exception (see EXCEPTIONS below). An unhandled exception will
-- 
cgit v1.2.3