unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* vc-next-action not behaving
@ 2005-05-26  1:10 David Abrahams
  2005-05-26  8:08 ` Andre Spiegel
  0 siblings, 1 reply; 11+ messages in thread
From: David Abrahams @ 2005-05-26  1:10 UTC (permalink / raw)



In recent CVS builds of emacs (on NT), when I do `C-x v v' on an
*unmodified* file under version control, and I get:

  File is edited but read-only; making it writable
  File is under version-control; use C-x v v to check in/out

The file was  *not* edited, but emacs seems confused about that.  I
know I went through this with emacs and vc years ago; I just changed
machines and it's happening again.  Kept my .emacs and my .cvsrc, so I
can't imagine what the problem is.

If I subsequently edit the file and then do `C-x v u' the file
reverts, but I am left with a writable file where I previously had a
read-only file.  I have CVSREAD=1 in my environment.

Can anyone suggest a fix for this problem?

Thanks,
-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2005-05-26 19:55 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-05-26  1:10 vc-next-action not behaving David Abrahams
2005-05-26  8:08 ` Andre Spiegel
2005-05-26 12:28   ` David Abrahams
2005-05-26 13:38     ` Andre Spiegel
2005-05-26 18:17       ` David Abrahams
2005-05-26 18:41         ` Andreas Schwab
2005-05-26 19:07           ` David Abrahams
2005-05-26 19:55             ` Andreas Schwab
2005-05-26 14:16     ` Stefan Monnier
2005-05-26 18:18       ` David Abrahams
2005-05-26 19:04         ` David Abrahams

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).