summaryrefslogtreecommitdiffstats
path: root/txr.1
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2011-11-19 20:43:13 -0800
committerKaz Kylheku <kaz@kylheku.com>2011-11-19 20:43:13 -0800
commit2cc166bafadd85ca85680997072c8380d039f8c9 (patch)
tree3b211dbf63e40fee98f62d2e30b3a6462efcab83 /txr.1
parent4ac284ddd4bbf4c3c02c0531795baf669bca4f54 (diff)
downloadtxr-2cc166bafadd85ca85680997072c8380d039f8c9.tar.gz
txr-2cc166bafadd85ca85680997072c8380d039f8c9.tar.bz2
txr-2cc166bafadd85ca85680997072c8380d039f8c9.zip
Bug #34866
* match.c (h_skip): Bugfix. Return the length of the line if the skip is to the end of line, not the value t. * txr.1: Clarify that @var@(skip)text is useless.
Diffstat (limited to 'txr.1')
-rw-r--r--txr.18
1 files changed, 7 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index f108639d..17c4307c 100644
--- a/txr.1
+++ b/txr.1
@@ -591,7 +591,7 @@ the trailing material did not occur.
A variable may be followed by a piece of text, a regular expression directive,
a function call, a directive, another variable, or nothing (i.e. occurs at the
-end of a line).
+end of a line). These cases are discussed in detail below.
.SS Variable Followed by Nothing
@@ -631,6 +631,12 @@ call, or a directive, the extent is determined by scanning the text
for the first position where a match occurs for the regular expression, call or
directive. (See Regular Expressions section below, and FUNCTIONS.)
+Note that the given variable and the function or directive are considered
+in isolation. This means, for instance, that @var@(skip)text is a degenerate
+form. The @(skip) will be processed alone, without regard for the trailing
+text and so consume the input to the end of the line. The right way to
+express the most probable intent of this is @{var}text.
+
.SS Consecutive Variables
If an unbound variable specified a fixed-width match or a regular expression,