From 441a46319c9165f1ef51d60eae5f5b783d5cc900 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 4 May 2005 17:24:49 +0000 Subject: [PATCH] (chmod invocation): chmod -w complains if its behavior differs from what chmod a-w would do. --- doc/coreutils.texi | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/coreutils.texi b/doc/coreutils.texi index e968afa39d..e24c11a77a 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -8451,9 +8451,11 @@ recursive directory traversals. If used, @var{mode} specifies the new permissions. For details, see the section on @ref{File permissions}. -In the extremely rare cases where @var{mode} has leading @samp{-}, a -portable script should use @option{--} first, e.g., @samp{chmod -- -w -file}. Typically, though, @samp{chmod a-w file} is preferable. +If you really want @var{mode} to have a leading @samp{-}, you should +use @option{--} first, e.g., @samp{chmod -- -w file}. Typically, +though, @samp{chmod a-w file} is preferable, and @command{chmod -w +file} (without the @option{--}) complains if it behaves differently +from what @samp{chmod a-w file} would do. The program accepts the following options. Also see @ref{Common options}. -- 2.47.3