Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <37E04038.E99DED63@pop.scriptics.com> Date: Wed, 15 Sep 1999 17:56:24 -0700 From: Mike Thomas Reply-To: wart AT scriptics DOT com X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com Subject: test -w broken on bash? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm running cygwin-b20 on Windows NT. When I run the bash.exe included in the package, I see the following behaviour: bash% umask 000 bash% touch foo bash% if test -w foo ; then echo foo ; fi bash% No echo. The file exists, but "test -w" doesn't think it's writable. But when I run sh.exe from the same Cygwin installation: sh% umask 0000 sh% touch foo sh% if test -w foo ; then echo foo ; fi foo sh% The echo is there. Is this a bug in bash or is it intended behaviour? Does test -w have a different meaning under bash? --Mike -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com