m4-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to m4/doc/m4.texinfo,v


From: Eric Blake
Subject: Changes to m4/doc/m4.texinfo,v
Date: Tue, 05 Sep 2006 17:28:46 +0000

CVSROOT:        /sources/m4
Module name:    m4
Changes by:     Eric Blake <ericb>      06/09/05 17:28:45

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- doc/m4.texinfo      5 Sep 2006 13:25:24 -0000       1.40
+++ doc/m4.texinfo      5 Sep 2006 17:28:45 -0000       1.41
@@ -377,7 +377,7 @@
 Then in 2005 Gary V. Vaughan collected together the many
 patches to @acronym{GNU} @code{m4} 1.4 that were floating around the net and
 released 1.4.3 and 1.4.4.  And in 2006, Eric Blake joined the team and
-prepared patches for the release of 1.4.5 and 1.4.6.
+prepared patches for the release of 1.4.5, 1.4.6, and 1.4.7.
 
 Meanwhile, development was underway for new features for @code{m4},
 such as dynamic module loading and additional builtins, practically
@@ -496,7 +496,7 @@
 @item --import-environment
 Imports every variable in the environment as a macro.  This is done
 before @option{-D} and @option{-U}, so they can override the
-enviroment.
+environment.
 
 @item -B @var{DIRECTORY}
 @itemx address@hidden
@@ -2651,7 +2651,7 @@
 Show the name of the current input file in each trace output line.
 
 @item l
-Show the the current input line number in each trace output line.
+Show the current input line number in each trace output line.
 
 @item p
 Print a message when a named file is found through the path search
@@ -3000,7 +3000,7 @@
 Characters that themselves, alone, form macro names.  No default.
 
 @item Escape
-Characters that must precede macro names for them to be recognised.  No
+Characters that must precede macro names for them to be recognized.  No
 default.
 
 @end table
@@ -3155,7 +3155,7 @@
 
 Macro calls can be given a @TeX{} or Texinfo like syntax using an
 escape.  If one or more characters are defined as escapes macro names
-are only recognised if preceded by an escape character.
+are only recognized if preceded by an escape character.
 
 If the escape is not followed by what is normally a word (a letter
 optionally followed by letters and/or numerals), that single character
@@ -3208,7 +3208,7 @@
 
 There is obviously an overlap with @code{changecom} and
 @code{changequote}.  Comment delimiters and quotes can now be defined in
-two different ways.  To avoid incompatibilites, if the quotes are set
+two different ways.  To avoid incompatibilities, if the quotes are set
 with @code{changequote}, all characters marked in the syntax table as
 quotes will be unmarked, leaving only one set of defined quotes as
 before.  Since the quotes are syntax attributes rather than syntax
@@ -3269,7 +3269,7 @@
 Note how it is possible to have both long and short quotes, if
 @code{changequote} is used before @code{changesyntax}.
 
-The syntax table is initialiased to be backwards compatible, so if you
+The syntax table is initialized to be backwards compatible, so if you
 never call @code{changesyntax}, nothing will have changed.
 
 Debugging output continue to use @kbd{(}, @kbd{,} and @kbd{)} to show
@@ -4960,13 +4960,15 @@
 diversion were made, and not where it was inserted again.
 
 @item
-GNU @code{m4} makes no attempt at prohiting autoreferential definitions
+GNU @code{m4} makes no attempt at prohibiting self-referential definitions
 like:
 
 @comment ignore
 @example
 define(`x', `x')
address@hidden
 define(`x', `x ')
address@hidden
 @end example
 
 There is nothing inherently wrong with defining @samp{x} to




reply via email to

[Prev in Thread] Current Thread [Next in Thread]