From: Richard Stanton <stanton@haas.berkeley.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "8924@debbugs.gnu.org" <8924@debbugs.gnu.org>
Subject: bug#8924: 23.3; Editing is rather difficult using vc with RCS backend
Date: Fri, 24 Jun 2011 13:46:43 -0700 [thread overview]
Message-ID: <40C7B1BFC291ED4E9D10436D07736A3346F8B2DE5F@EXMAIL7.haas.uc.berkeley.edu> (raw)
In-Reply-To: <83tybft52b.fsf@gnu.org>
> From: Eli Zaretskii [mailto:eliz@gnu.org]
> Sent: Friday, June 24, 2011 12:15 PM
> To: Richard Stanton
> Cc: 8924@debbugs.gnu.org
> Subject: Re: bug#8924: 23.3; Editing is rather difficult using vc with RCS
> backend
>
> > I may well be missing something obvious, but I can't find an RCS port at the
> GnuWin32 site.
>
> Looks like they removed it. Perhaps because I reported a few bad bugs with
> their port. I actually use a fixed port I built myself; I should have mentioned
> that, sorry.
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. Now I just need to track down a working non-Cygwin version of RCS...
Thanks for all your help.
next prev parent reply other threads:[~2011-06-24 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 21:20 bug#8924: 23.3; Editing is rather difficult using vc with RCS backend Richard Stanton
2011-06-24 9:14 ` Eli Zaretskii
2011-06-24 16:03 ` Richard Stanton
2011-06-24 17:23 ` Eli Zaretskii
2011-06-24 18:13 ` Richard Stanton
2011-06-24 19:14 ` Eli Zaretskii
2011-06-24 20:46 ` Richard Stanton [this message]
2011-06-25 6:31 ` Eli Zaretskii
2011-06-24 18:20 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40C7B1BFC291ED4E9D10436D07736A3346F8B2DE5F@EXMAIL7.haas.uc.berkeley.edu \
--to=stanton@haas.berkeley.edu \
--cc=8924@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).