[Top][All Lists]

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

Re: creating temporary files in a secure way

From: Paul Eggert
Subject: Re: creating temporary files in a secure way
Date: Tue, 08 Feb 2005 09:29:19 -0800
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Thanks for proofreading that.  I installed this further patch:

2005-02-08  Paul Eggert  <address@hidden>

        * doc/autoconf.texi (Special Shell Variables): Clarify
        PATH_SEPARATOR wording; fix typo in IFS.  Reported by Gary V. Vaughan.

--- autoconf.texi       8 Feb 2005 00:35:01 -0000       1.876
+++ autoconf.texi       8 Feb 2005 17:27:04 -0000       1.877
@@ -10487,7 +10487,7 @@ PS4='+ '
 @item IFS
 @evindex IFS
 Long ago, shell scripts inherited @env{IFS} from the environment,
-but this caused many problems so modern shells any environment
+but this caused many problems so modern shells ignore any environment
 settings for @env{IFS}.
 Don't set the first character of @code{IFS} to backslash.  Indeed,
@@ -10650,11 +10650,10 @@ your script might be suspended waiting f
 On @acronym{DJGPP} systems, the @env{PATH_SEPARATOR} environment
 variable can be set to either @samp{:} or @samp{;} to control the path
 separator Bash uses to set up certain environment variables (such as
address@hidden).  If you want @command{configure} to detect the regular
address@hidden path separator (@samp{;}), so it can be safely substituted
-in files that may not support @samp{;} as a path separator, then unset
-this variable or set it to @samp{;}.  @xref{File System Conventions},
-for more information about @code{PATH_SEPARATOR}.
address@hidden).  You can set this variable to @samp{;} if you want
address@hidden to use @samp{;} as a separator; this might be useful
+if you plan to use non-Posix shells to execute files.  @xref{File System
+Conventions}, for more information about @code{PATH_SEPARATOR}.
 @item PWD
 @evindex PWD

reply via email to

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