summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2011-11-09 23:30:56 -0800
committerKaz Kylheku <kaz@kylheku.com>2011-11-09 23:30:56 -0800
commitffac180e902b5e5bcf32872d6197b8c7800a2ed2 (patch)
treebd3f6a675702db91cfedadff0e9c1e3c41b7af4d
parent7ab6eb327d444c4c37c9ebef0cbcebe25024298d (diff)
downloadtxr-ffac180e902b5e5bcf32872d6197b8c7800a2ed2.tar.gz
txr-ffac180e902b5e5bcf32872d6197b8c7800a2ed2.tar.bz2
txr-ffac180e902b5e5bcf32872d6197b8c7800a2ed2.zip
Minor.
-rw-r--r--txr.12
1 files changed, 1 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index ad265ef4..dc7e78ba 100644
--- a/txr.1
+++ b/txr.1
@@ -2807,7 +2807,7 @@ This kind of definition is actually considered to be in the vertical context,
and like other directives that have special effects and that do not match
anything, it does not consume a line of input. If the above syntax were
allowed, it would mean that the line would not only define a function but also
-match "lalala". This would, in turn, would mean that the @(define) is
+match "lalala". This would, in turn, would mean that the @(define)...@(end) is
actually in horizontal mode, and so it matches a span of zero characters within
a line (which means that is would require a line of input to match: a nasty
thing for a non-matching directive to do!)