This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: After Cygwin and XEmacs upgrade, read-only files aren't detected

>>>>> "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

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++

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]