Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: After Cygwin and XEmacs upgrade, read-only files aren't detected References: <868z0cqurm DOT fsf AT earthlink DOT net> From: dmkarr AT earthlink DOT net (David M. Karr) Date: 02 Nov 2002 20:16:02 -0800 In-Reply-To: <868z0cqurm.fsf@earthlink.net> Message-ID: <86fzujcmpp.fsf@earthlink.net> Lines: 27 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence (RC5 Windows)) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>>>> "David" == David M Karr 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/