* txr.1: Fix inaccuracies: files are not read into memory all at

once, and a query doesn't execute if it had errors.

2 files changed, 10 insertions, 5 deletions

diff --git a/ChangeLog b/ChangeLog
index 779837b5..bbbd0620 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,9 @@
-2010-01-26  Kaz Kylheku  <kkylheku@gmail.com>
+2010-03-01  Kaz Kylheku  <kkylheku@gmail.com>
+
+	* txr.1: Fix inaccuracies: files are not read into memory all at
+	once, and a query doesn't execute if it had errors.
+
+2010-02-28  Kaz Kylheku  <kkylheku@gmail.com>
 
 	Version 034
 
diff --git a/txr.1 b/txr.1
index 705f98bc..7f9c4d11 100644
--- a/txr.1
+++ b/txr.1
@@ -204,10 +204,10 @@ file.
 .PP
 .B txr
 begins by reading the query. The entire query is scanned, internalized
-and then begins executing.  No file is opened until the query calls for a match
-for material from that file, but once opened, a file is always read in its
-entirety and stored in memory. A query may complete (successfully or not)
-before opening some or all of the files.
+and then begins executing, if it is free of syntax errors.  The reading of
+data, on the other hand, is lazy.  A file isn't opened until the query demands
+material from that file, and then the contents are read on demand, not all at
+once.
 
 If no files arguments are specified on the command line, it is up to the
 query to open a file, pipe or standard input via the @(next) directive