🚀 go-pugleaf

mi@rtfm.ziplink.net (Mikhail Teterin) writes:

> how to turn this "feature" off? Here is what happens. I check out
> a file on my FreeBSD machine. My colleague works with Emacs on NT
> (shame on him, but what can I do?). As we know, NT does not have
> ``rcs'', but Emacs thinks it is smarter then it's users (true for
> many cases). So, it sees the RCS subdirectory next to the file my
> colleague wants to edit, and insists on the file being either
> read-only, or wants to check-it out (which fails due to the lack
> of rcs).
> 

I had this exact same problem just a few days ago.  I waas needing to
edit a file, but filename.c,v existed also.  emacs was trying to check
it out, and when it did not check it out, it made it read only.  even
with the permissions set to 777.  ugh.  what I ended up doing was
nuking all the *,v files in the directory.  I believe I would have
been fine with a rename of the file to newfilename.c, but I am not
sure.  As long as RCS garbage did not hang around for the filename,
then emacs would not have been messing with rcs permissions and such.

however, I bet there is a port of rcs for nt.  I suggest searching on
the net for ntemacs, and / or the virtunix stuff.  that might turn up
an NT port of rcs for you all to use.

l8r,
rob



> How do I make it write to the file, damn it?! Unix permissions are
> just fine, what is it's problem?!?
> 
> TIA,
> 
> 	-mi
> 
> -- 
> 	"Windows for dummies"