rename "ENVIRONMENT VARIABLES" section to "ENVIRONMENT" to be more standard

diff --git a/visudo.cat b/visudo.cat
index b8d034ba2ebf176e35c288ca5176c83c61434df8..963d31b01b781a478a0c08708cfde08dea08b5c7 100644 (file)
--- a/visudo.cat
+++ b/visudo.cat
@@ -61,7 +61,7 @@ E\bE\bE\bER\bR\bR\bRR\bR\bR\bRO\bO\bO\bOR\bR\bR\bRS\bS\bS\bS
 
 
 
-17/Aug/1999                    1.6                              1
+25/Aug/1999                    1.6                              1
 
 
 
@@ -82,19 +82,19 @@ VISUDO(8)              MAINTENANCE COMMANDS             VISUDO(8)
            complain).  In -\b-\b-\b-s\bs\bs\bs (strict) mode these are errors not
            warnings.
 
-F\bF\bF\bFI\bI\bI\bIL\bL\bL\bLE\bE\bE\bES\bS\bS\bS
-        /etc/sudoers           List of who can run what
-        /etc/sudoers.tmp       Lock file for visudo
-
-
-E\bE\bE\bEN\bN\bN\bNV\bV\bV\bVI\bI\bI\bIR\bR\bR\bRO\bO\bO\bON\bN\bN\bNM\bM\bM\bME\bE\bE\bEN\bN\bN\bNT\bT\bT\bT V\bV\bV\bVA\bA\bA\bAR\bR\bR\bRI\bI\bI\bIA\bA\bA\bAB\bB\bB\bBL\bL\bL\bLE\bE\bE\bES\bS\bS\bS
-       The following are used only if v\bv\bv\bvi\bi\bi\bis\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo was configured with
-       the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\be_\bn_\bv_\b-_\be_\bd_\bi_\bt_\bo_\br option:
+E\bE\bE\bEN\bN\bN\bNV\bV\bV\bVI\bI\bI\bIR\bR\bR\bRO\bO\bO\bON\bN\bN\bNM\bM\bM\bME\bE\bE\bEN\bN\bN\bNT\bT\bT\bT
+       The following environment variables are used only if
+       v\bv\bv\bvi\bi\bi\bis\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo was configured with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\be_\bn_\bv_\b-_\be_\bd_\bi_\bt_\bo_\br option:
 
         EDITOR                 Used by visudo as the editor to use
         VISUAL                 Used by visudo if EDITOR is not set
 
 
+F\bF\bF\bFI\bI\bI\bIL\bL\bL\bLE\bE\bE\bES\bS\bS\bS
+        /etc/sudoers           List of who can run what
+        /etc/sudoers.tmp       Lock file for visudo
+
+
 A\bA\bA\bAU\bU\bU\bUT\bT\bT\bTH\bH\bH\bHO\bO\bO\bOR\bR\bR\bR
        Many people have worked on _\bs_\bu_\bd_\bo over the years, this
        version of v\bv\bv\bvi\bi\bi\bis\bs\bs\bsu\bu\bu\bud\bd\bd\bdo\bo\bo\bo was written by:
@@ -127,7 +127,7 @@ S\bS\bS\bSE\bE\bE\bEE\bE\bE\bE A\bA\bA\bAL\bL\bL\bLS\bS\bS\bSO\bO\bO\bO
 
 
 
-17/Aug/1999                    1.6                              2
+25/Aug/1999                    1.6                              2
 
 
 
@@ -193,6 +193,6 @@ VISUDO(8)              MAINTENANCE COMMANDS             VISUDO(8)
 
 
 
-17/Aug/1999                    1.6                              3
+25/Aug/1999                    1.6                              3
 
 

diff --git a/visudo.html b/visudo.html
index 4c0e4f427d8d34af30e5ce68db171a46ba594317..9102098d47aeb13e53d0e1ee031ff3f5559bcb3a 100644 (file)
--- a/visudo.html
+++ b/visudo.html
@@ -15,8 +15,8 @@
        <LI><A HREF="#DESCRIPTION">DESCRIPTION</A>
        <LI><A HREF="#OPTIONS">OPTIONS</A>
        <LI><A HREF="#ERRORS">ERRORS</A>
+       <LI><A HREF="#ENVIRONMENT">ENVIRONMENT</A>
        <LI><A HREF="#FILES">FILES</A>
-       <LI><A HREF="#ENVIRONMENT_VARIABLES">ENVIRONMENT VARIABLES</A>
        <LI><A HREF="#AUTHOR">AUTHOR</A>
        <LI><A HREF="#BUGS">BUGS</A>
        <LI><A HREF="#DISCLAIMER">DISCLAIMER</A>
@@ -100,20 +100,20 @@ you have a user or hostname listed that consists solely of upper case
 letters, digits, and the underscore ('_') character. If the latter, you can
 ignore the warnings (<STRONG>sudo</STRONG> will not complain). In <STRONG>-s</STRONG> (strict) mode these are errors not warnings.
 
-<H1><A NAME="FILES">FILES</A></H1>
-<P>
-<PRE> /etc/sudoers           List of who can run what
- /etc/sudoers.tmp       Lock file for visudo
-</PRE>
-<H1><A NAME="ENVIRONMENT_VARIABLES">ENVIRONMENT VARIABLES</A></H1>
+<H1><A NAME="ENVIRONMENT">ENVIRONMENT</A></H1>
 <P>
-The following are used only if <STRONG>visudo</STRONG> was configured with the
-<EM>--with-env-editor</EM> option:
+The following environment variables are used only if <STRONG>visudo</STRONG>
+was configured with the <EM>--with-env-editor</EM> option:
 
 <P>
 <PRE> EDITOR                 Used by visudo as the editor to use
  VISUAL                 Used by visudo if EDITOR is not set
 </PRE>
+<H1><A NAME="FILES">FILES</A></H1>
+<P>
+<PRE> /etc/sudoers           List of who can run what
+ /etc/sudoers.tmp       Lock file for visudo
+</PRE>
 <H1><A NAME="AUTHOR">AUTHOR</A></H1>
 <P>
 Many people have worked on <EM>sudo</EM> over the years, this version of

diff --git a/visudo.man b/visudo.man
index 07a4a8949539777881f52c82d82f969fcc3a9874..f1601aa48cd9f7a38bfdc03dbe621de183edad4f 100644 (file)
--- a/visudo.man
+++ b/visudo.man
@@ -2,10 +2,8 @@
 ''' $RCSfile$$Revision$$Date$
 '''
 ''' $Log$
-''' Revision 1.10  1999/08/17 15:29:47  millert
-''' o NewArgv and NewArgc don't need to be externally visible.
-''' o If pedantic > 1, it is a parse error.
-''' o Add -s (strict) option to visudo which sets pedantic to 2.
+''' Revision 1.11  1999/08/26 09:08:31  millert
+''' rename "ENVIRONMENT VARIABLES" section to "ENVIRONMENT" to be more standard
 '''
 '''
 .de Sh
@@ -98,7 +96,7 @@
 .nr % 0
 .rr F
 .\}
-.TH VISUDO 8 "1.6" "17/Aug/1999" "MAINTENANCE COMMANDS"
+.TH VISUDO 8 "1.6" "25/Aug/1999" "MAINTENANCE COMMANDS"
 .UC
 .if n .hy 0
 .if n .na
@@ -245,19 +243,19 @@ consists solely of upper case letters, digits, and the
 underscore ('_') character.  If the latter, you can ignore
 the warnings (\fBsudo\fR will not complain).  In \fB\-s\fR (strict)
 mode these are errors not warnings.
-.SH "FILES"
+.SH "ENVIRONMENT"
+The following environment variables are used only if \fBvisudo\fR
+was configured with the \fI--with-env-editor\fR option:
 .Sp
 .Vb 2
-\& /etc/sudoers           List of who can run what
-\& /etc/sudoers.tmp       Lock file for visudo
+\& EDITOR                 Used by visudo as the editor to use
+\& VISUAL                 Used by visudo if EDITOR is not set
 .Ve
-.SH "ENVIRONMENT VARIABLES"
-The following are used only if \fBvisudo\fR was configured with the
-\fI--with-env-editor\fR option:
+.SH "FILES"
 .Sp
 .Vb 2
-\& EDITOR                 Used by visudo as the editor to use
-\& VISUAL                 Used by visudo if EDITOR is not set
+\& /etc/sudoers           List of who can run what
+\& /etc/sudoers.tmp       Lock file for visudo
 .Ve
 .SH "AUTHOR"
 Many people have worked on \fIsudo\fR over the years, this version of
@@ -308,9 +306,9 @@ the editor used by \fBvisudo\fR allows shell escapes.
 
 .IX Item "Warning: undeclared Alias referenced near ..."
 
-.IX Header "FILES"
+.IX Header "ENVIRONMENT"
 
-.IX Header "ENVIRONMENT VARIABLES"
+.IX Header "FILES"
 
 .IX Header "AUTHOR"
 

diff --git a/visudo.pod b/visudo.pod
index 4d22e2ef05a781cdad75d912d5cfbe575d84bfad..fff6b0ef5732ace8d5bd962348b5adb02356989e 100644 (file)
--- a/visudo.pod
+++ b/visudo.pod
@@ -115,19 +115,19 @@ underscore ('_') character.  If the latter, you can ignore
 the warnings (B<sudo> will not complain).  In B<-s> (strict)
 mode these are errors not warnings.
 
-=head1 FILES
-
- /etc/sudoers          List of who can run what
- /etc/sudoers.tmp      Lock file for visudo
-
-=head1 ENVIRONMENT VARIABLES
+=head1 ENVIRONMENT
 
-The following are used only if B<visudo> was configured with the
-I<--with-env-editor> option:
+The following environment variables are used only if B<visudo>
+was configured with the I<--with-env-editor> option:
 
  EDITOR                        Used by visudo as the editor to use
  VISUAL                        Used by visudo if EDITOR is not set
 
+=head1 FILES
+
+ /etc/sudoers          List of who can run what
+ /etc/sudoers.tmp      Lock file for visudo
+
 =head1 AUTHOR
 
 Many people have worked on I<sudo> over the years, this version of