[latexrefman-commits] [SCM] latexrefman updated: r718 - trunk

[karl at gnu.org.ua]

Author: karl
Date: 2018-10-22 21:07:42 +0300 (Mon, 22 Oct 2018)
New Revision: 718

Modified:
   trunk/ChangeLog
   trunk/latex2e.texi
Log:
small changes to \write text and examples

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog	2018-10-22 11:30:23 UTC (rev 717)
+++ trunk/ChangeLog	2018-10-22 18:07:42 UTC (rev 718)
@@ -1,3 +1,7 @@
+2018-10-22  Karl Berry  <karl at freefriends.org>
+
+	* latex2e.texi (\write, etc.): small changes to text and examples.
+
 2018-10-21  Jim Hefferon  <jhefferon at smcvt.edu>
 
 	* latex2e.texi  Add \read.

Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi	2018-10-22 11:30:23 UTC (rev 717)
+++ trunk/latex2e.texi	2018-10-22 18:07:42 UTC (rev 718)
@@ -18666,7 +18666,7 @@
 opened by @code{\openout}.  For instance, @code{\write6} writes to text
 stream number at tie{}6.
 
-If this appears in @file{@var{basefile}.tex} then it opens
+If the following appears in @file{@var{basefile}.tex} then it opens
 @file{@var{basefile}.jh}, writes @samp{Hello World!} and a newline to
 it, and closes that file.
 
@@ -18674,9 +18674,9 @@
 \newwrite\myfile
 \immediate\openout\myfile=\jobname.jh   % \jobname is current file name
   ...
-\write\myfile@{Hello world!@}
+\immediate\write\myfile@{Hello world!@}
   ...
-\closeout\myfile
+\immediate\closeout\myfile
 @end example
 
 @noindent
@@ -18698,7 +18698,7 @@
 puts @samp{Hello World!} followed by a newline in the terminal output.
 (But 16, 17, and 18 are special as @var{number}; see below.)
 
-In Lua at LaTeX{}, instead of 16 output streams there are 256
+In Lua at TeX{}, instead of 16 output streams there are 256
 (@pxref{@TeX{} engines}).
 
 Write to the current @file{.aux} file, which is associated with the main
@@ -18760,11 +18760,11 @@
 \wlog@{Parallel lines have a lot in common.^^JBut they never meet.@}
 @end example
 
-The ability to Write files raises security issues.  If you compiled a
+The ability to write files raises security issues. If you compiled a
 downloaded @LaTeX{} file and it overwrote your password file then you
-would be annoyed.  @TeX{} systems by default only allow you to open
-files for writing that are in the current directory or in a
-subdirectory.  This
+would be justifiably troubled. @TeX{} systems by default only allow
+you to open files for writing that are in the current directory or in
+a subdirectory. This
 
 @example
 \newwrite\jhfile
@@ -18814,7 +18814,7 @@
 With this example document body.
 
 @example
-before\message@{One Two@}\message@{Three@} \message@{Four^^JI@}
+before\message@{One Two@}\message@{Three@}\message@{Four^^JI@}
 \message@{declare a thumb war.@}After
 @end example
 
@@ -18828,7 +18828,8 @@
 
 @noindent
 Note that @code{^^J} produces a newline.  Also, in the output document,
-between @samp{before} and @samp{After} will be a single space.
+between @samp{before} and @samp{After} will be a single space (from
+the end of line following @samp{I@}}).
 
 While @code{\message} allows you more control over formatting
 interaction lines, a gotcha is that @LaTeX{} may mess up your formatting
@@ -18837,7 +18838,7 @@
 one given above.
 
 @example
-before\message@{One@}\message@{Two Three@} \message@{Four^^JI@}
+before\message@{One@}\message@{Two Three@}\message@{Four^^JI@}
 \message@{declare a thumb war.@}After
 @end example