[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#8924: 23.3; Editing is rather difficult using vc with RCS backend

From: Eli Zaretskii
Subject: bug#8924: 23.3; Editing is rather difficult using vc with RCS backend
Date: Sat, 25 Jun 2011 09:31:48 +0300

> From: Richard Stanton <address@hidden>
> CC: "address@hidden" <address@hidden>
> Date: Fri, 24 Jun 2011 13:46:43 -0700
> I did a little more testing, and it looks like the problem is indeed a Cygwin 
> vs. non-Cygwin issue. On first checking in the file, I reported that the 
> buffer remains read/write while the file itself is read-only. It turns out 
> there's a little more to it:
> I reported it being read-only after running the (Cygwin) ls command:
> C:\projects\test\version\rcstest>ls -l test.tex
> -r-x------+ 1 stanton None 84 Jun 24 13:40 test.tex
> However, DOS doesn't see it as read-only, which explains why Emacs leaves the 
> buffer writable:
> C:\projects\test\version\rcstest>attrib test.tex
> A            C:\projects\test\version\rcstest\test.tex
> If I manually set the file to read only using attrib +R, then reload the file 
> into Emacs,
> a. The buffer is now read-only, and I can't edit it until I press C-x v v 
> again to check it out. Now everything works OK.
> b. The $Id$ header issue has also gone away.
> So it seems to be an inconsistency between the way DOS and Cygwin keep track 
> of file attributes.

Yes, that figures.  Cygwin uses NTFS ACLs to emulate Posix file
permissions, and does not set the DOS Readonly attribute to match the
ACLs.  The native Emacs build does not pay attention to the NTFS ACLs,
so it doesn't know the file was made read-only.

I'm closing this bug report.

> Now I just need to track down a working non-Cygwin version of RCS...

I sent my binaries off-list.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]