Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	Re: After Cygwin and XEmacs upgrade, read-only files aren't detected
From:	Mark Harig <mharig AT erols DOT com>
To:	"David M. Karr" <dmkarr AT earthlink DOT net>
Cc:	cygwin AT cygwin DOT com
In-Reply-To:	<86fzujcmpp.fsf@earthlink.net>
References:	<868z0cqurm DOT fsf AT earthlink DOT net> <86fzujcmpp DOT fsf AT earthlink DOT net>
Date:	03 Nov 2002 00:41:44 -0500
Message-Id:	<1036302107.1130.11.camel@localhost.localdomain>
Mime-Version:	1.0

With the most recent version of Cygwin, 1.3.14, CYGWIN has been set to 
'ntsec' by default.  Unfortunately, this doesn't show up in the output 
of 'cygcheck -s -r -v'.  

You might want to consider running the Microsoft 'convert' utility on 
your disk to convert your filesystem from FAT32 to NTFS. 

On Sat, 2002-11-02 at 23:16, David M. Karr wrote:
> >>>>> "David" == David M Karr <dmkarr AT earthlink DOT net> writes:
> 
>     David> Last night I upgraded my Cygwin and Cygwin/XEmacs installations to the latest.
>     David> Today, I noticed that XEmacs can no longer notice that read-only files are
>     David> read-only.  Normally, it detects that, and sets the buffer to be read-only.
> 
>     David> I did report this to the XEmacs group, but they're not aware of any recent
>     David> changes that could be related to this.
> 
>     David> Is there some recent Cygwin feature change that could be causing this?
> 
> I discovered that if I change my CYGWIN variable from "tty" to "tty nontsec"
> this now behaves as I would expect, showing a read-only buffer for a read-only
> file.
> 
> Before discovering this, I also noticed that if a file only had the "read" bits
> on, then XEmacs would see it was read-only.  However, if the file had both the
> read AND execute bits on (still not having any write bits), then XEmacs would
> think it was writable.
> 
> Testing the same situation with "vi" showed a read-only buffer, both before and
> after changing the CYGWIN variable.
> 
> -- 
> ===================================================================
> David M. Karr          ; Java/J2EE/XML/Unix/C++
> dmkarr AT earthlink DOT net
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -