From 062b374c59842e6f00e1df7acf0cbe33293026af Mon Sep 17 00:00:00 2001 From: Kaz Kylheku Date: Sat, 21 Jan 2017 23:47:22 -0800 Subject: doc: missing :var documented. txr.1: the @(next) directive has a :var argument which was added in 2011 but never documented. --- txr.1 | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'txr.1') diff --git a/txr.1 b/txr.1 index 479b604c..d99d4e88 100644 --- a/txr.1 +++ b/txr.1 @@ -3365,6 +3365,7 @@ and takes various arguments, according to these possibilities: .mets @(next :list << lisp-expr ) .mets @(next :tlist << bind-expr ) .mets @(next :string << lisp-expr ) +.mets @(next :var << var ) .mets @(next nil) .cble @@ -3463,6 +3464,30 @@ except that .meta bind-expr is not a \*(TL expression, but a \*(TX bind expression. +The syntax +.cblk +.meti @(next :var << var ) +.cble +requires +.meta var +to be a previously bound variable. The value of the +variable is retrieved and treated like a list, in the +same manner as under +.codn "@(next :list ...)" . +Note that +.code "@(next :var x)" +is not always the same as +.codn "@(next :tlist x)" , +because +.code ":var x" +strictly requires +.code x +to be a \*(TX variable, whereas the +.code x +in +.code ":tlist x" +is an expression which can potentially refer to Lisp variable. + The syntax .cblk .meti @(next :string << lisp-expr ) -- cgit v1.2.3