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

karl at gnu.org.ua karl at gnu.org.ua
Mon Apr 13 00:46:18 CEST 2020


Author: karl
Date: 2020-04-13 01:46:18 +0300 (Mon, 13 Apr 2020)
New Revision: 788

Modified:
   trunk/ChangeLog
   trunk/latex2e.texi
Log:
\message refinements

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog	2020-04-12 14:19:53 UTC (rev 787)
+++ trunk/ChangeLog	2020-04-12 22:46:18 UTC (rev 788)
@@ -1,3 +1,8 @@
+2020-04-12  Karl Berry  <karl at freefriends.org>
+
+	* latex2e.texi (\message): remove "interaction lines",
+	other wording.
+
 2020-04-12  Vincent Belaïche  <vincentb1 at users.sourceforge.net>
 
 	* latex2e-fr.texi (\include & \includeonly): Complete translation.

Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi	2020-04-12 14:19:53 UTC (rev 787)
+++ trunk/latex2e.texi	2020-04-12 22:46:18 UTC (rev 788)
@@ -19899,15 +19899,14 @@
 @end example
 
 @noindent
-Note that @code{^^J} produces a newline.  Also, in the output document,
+The @code{^^J} produces a newline.  Also, in the output document,
 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 because it inserts line breaks depending on what it has
-already written. Contrast this document body, where the @samp{Two} has
-moved, to the one given above.
+While @code{\message} allows you more control over formatting, a
+gotcha is that @LaTeX{} may mess up that formatting because it inserts
+line breaks depending on what it has already written. Contrast this
+document body, where the @samp{Two} has moved, to the one given above.
 
 @example
 before\message@{One@}\message@{Two Three@}\message@{Four^^JI@}
@@ -19920,7 +19919,8 @@
 it and the @samp{Two Three}.  That line break appears also in the log
 file.  This line break insertion can depend on, for instance, the length
 of the full path names of included files.  So producing finely-formatted
-lines in a way that is portable is hard.
+lines in a way that is portable is hard, likely requiring 
+starting your message at the beginning of a line.
 
 
 @node \wlog



More information about the latexrefman-commits mailing list.