Hello! I'm studying the GNU Coding Standards (in hope to contribute to the GNUpdf), and I have a minor suggestion to the standards document.
In my opinion mentioning "set -C" is not very clear. It needs a bit more explanation. Of course I could be wrong but in case it misled me (and I do have some practical experience with bash scripting) it could mislead or confuse the others who reads the standard as well. My suggestion (along with my doubts as comments) are placed below. Note: The "---" version corresponds to this: http://cvs.savannah.gnu.org/viewvc/*checkout*/gnustandards/standards.texi?revision=1.201&root=gnustandards Best regards, Michael. D:\...shared_repos\gnustandards\mivael>bzr diff === modified file 'standards.texi' --- standards.texi 2011-01-24 09:47:11 +0000 +++ standards.texi 2011-01-24 10:28:12 +0000 @@ -703,7 +703,12 @@ @noindent or by using the @code{mkstemps} function from libiberty. -In bash, use @code{set -C} to avoid this problem. +In bash scripts, use @code{set -C} (@code{set -o noclobber}) +to avoid this problem. +@c But, anyway, how this prevents from creating world readable files? +@c According to the bash man page, noclobber should prevent from +@c unintentional truncating to zero size of existing files, +@c but in case file doesn't exist, it just created. -- mivael @node Libraries @section Library Behavior -- Michael V. Antosha http://identi.ca/mivael
